emergency_contacts

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the word 'query' implies a read-only operation, but this is not explicitly stated. The description offers example filter/order structures but omits pagination behavior, return format, and the customer_slug header override semantics, which are left to the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, compact line with a dense example JSON. It is efficient and front-loaded, though the large example may reduce readability. No filler words are present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema or return-value description is provided, so the agent cannot infer what the tool returns. The tool's purpose as a paginated list query is implied but not stated, and the interaction with customer_slug is only in the schema. The description is not complete for a 5-parameter query tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema descriptions are minimal ('GraphQL: String'), but the example variable block adds concrete meaning for after, first, filter, and order, showing nested structures like callCategories and greyMatterUser. This goes beyond the schema, though customer_slug is only covered by the schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description indicates 'query emergencyContacts' with plural, implying a list operation, and distinguishes from the singular sibling 'emergency_contact'. However, it does not explicitly say 'list all' or 'search', so the purpose is clear but not maximally specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives like 'emergency_contact' (singular) or create/update/delete variants. The description only provides a query template, not usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.