All 5 tools have basic descriptions and parameter schemas, but quality is inconsistent. Descriptions are generic (10-60 chars) and lack actionable context for LLM selection. Parameter schemas exist but lack type specificity, 'filter' and 'orderBy' are typed as 'object' and 'array' with minimal guidance on structure. No output schemas documented. No error handling guidance. Tools follow verb_noun naming (get_*) but descriptions do not explain WHEN to use each tool or what distinguishes them. No tool annotations (readOnlyHint, etc.). Pagination parameters present but no documented result limits or total count fields.

• Expand tool descriptions to 80-150 chars. Example: 'get_loomers: Retrieve a paginated list of Loomers (employees) with optional filtering by area, hire date, or name. Use this to discover Loomers before querying their form responses. Returns up to 50 records per page.'
• Document 'filter' and 'orderBy' parameter structure explicitly. Example: 'filter: Object with keys like {areaId: string, name: string, hireDate: string}. orderBy: Array of {field: string, direction: "AscNullsFirst"|"AscNullsLast"|"DescNullsFirst"|"DescNullsLast"}.'
• Add output schema documentation to each tool. Example: 'Returns {edges: [{cursor: string, node: {id, name, email, areaId}}], pageInfo: {endCursor, hasNextPage, startCursor}}'.
• Add readOnlyHint: true to all tool schemas to signal to agents these are safe to retry without side effects.
• Document result limits in descriptions. Example: 'Returns up to 50 Loomers per page. Use pagination (after cursor) to fetch additional records.'