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

No annotations are provided, so the description carries the full behavioral burden. 'Reversible' is useful, but it does not say whether moving triggers notifications, automation side effects, required permissions, or what happens to existing stage history.

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?

One dense sentence pair: operation, routing key, id source, and reversibility. No filler; front-loaded.

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 2-param mutation with no annotations and no output schema, the description covers the core action and id sourcing but omits side effects, permissions, and parameter formats that an agent would need to call it confidently.

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?

Schema coverage is 0% and neither param is described in the schema. The description clarifies that stage_id is a stage identifier sourced from crm_list_stages, and that id is the lead, but does not state the format (integer/UUID) or that both are required strings.

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?

States a specific verb + resource ('move a lead to a different pipeline stage') and the routing key ('by stage_id'). Distinguishes itself cleanly from crm_update_lead (full edit) and crm_reassign_crm_lead (ownership change).

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?

Names the prerequisite helper (get ids from crm_list_stages), which is the key when-to-use context. Does not explicitly exclude crm_update_lead for the same operation, so it falls short of 5.

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