Set lead status

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

Adds context about recording update time, which is beyond annotations. However, does not disclose side effects (e.g., workflow triggers) or permission requirements. Annotations indicate idempotent but non-read-only.

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?

Single sentence, no redundancy, directly conveys the core action and records update time.

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?

Lacks parameter explanations for id and project, no mention of return values or error handling. Incomplete for a tool with 3 required params and no output schema.

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 has 0% description coverage. Description only lists the enum values for status but does not explain 'id' or 'project' parameters, leaving the agent to infer their meaning.

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 uses a specific verb 'Move' and resource 'lead', lists the exact pipeline stages, and clearly distinguishes from sibling tools like 'convert_lead' or 'enrich_lead'.

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 guidance on when to use this tool versus alternatives (e.g., convert_lead). Does not mention prerequisites or conditions for valid transitions.

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