list_contact_stages

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

The description only states that the tool returns id/label pairs, without disclosing any behavioral traits such as permissions, side effects, or rate limits. No annotations are provided, so the description carries the full burden but falls short.

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 consists of two short, clear sentences with no redundancy. It is front-loaded with the purpose and immediately provides the return structure.

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?

Given the tool's simplicity and the presence of an output schema, the description adequately explains the tool's function. However, it could be more explicit about the context (sales pipeline) to fully differentiate from the hiring pipeline stage 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?

With zero parameters, the description adds value by explaining the output format (id/label pairs) beyond the input schema. The schema coverage is 100%, but the description clarifies what each returned field represents.

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 clearly states the tool lists sales pipeline stages (contact stages) and specifies the return format of {id, label} pairs. This distinguishes it from sibling tool list_hiring_pipeline_stages, which lists stages for hiring pipelines.

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?

The description implies usage for retrieving contact stages in a sales pipeline, but provides no explicit guidance on when to use this tool over alternatives, nor any exclusions or prerequisites.

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