update_call_order

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely labels the mutation and lists variables, with no mention of side effects, permissions, whether it replaces existing data, or any other behavioral context. It is essentially a stub.

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 very short, but it is under-specified rather than effectively concise. It lacks an actual explanation of the tool's purpose and parameter roles, making it a cryptic fragment rather than a well-structured description.

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?

For a simple mutation tool, the description is incomplete. It does not explain the effect of updating call order, how id is used, or mention the optional customer_slug parameter. The description is insufficient for an agent to understand when and how to invoke the tool correctly.

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?

All parameters have schema descriptions, though they are minimal ('GraphQL: Int!'). The description adds an example variable mapping, which provides a small amount of practical guidance, but it does not clarify the semantics of callOrder or id beyond the schema. Baseline 3 is appropriate.

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 provides the domain ('Emergency Contacts') and the operation name ('mutation updateCallOrder'), but it essentially restates the tool name without explaining what the mutation does. It does not explicitly state that it updates the order of an emergency contact, nor does it distinguish itself from sibling tools like update_emergency_contact.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus other emergency contact tools or similar update operations. There are no prerequisites, scenarios, or alternative recommendations.

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