get_stages

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 fails to indicate whether this is a read-only/safe operation, expected data volume, pagination behavior, or any side effects. The verb 'Get' implies reading but lacks explicit safety confirmation.

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 extremely brief (three words) with no structural issues or wasted text. However, its brevity results in under-specification rather than efficient information delivery.

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 presence of closely related siblings ('get_stage', 'get_pipeline', 'get_pipelines') and the lack of output schema, the description inadequately explains the tool's behavior. It omits critical context about default behavior when optional parameters are missing and retrieval scope.

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 description coverage is 100% ('Filter stages by pipeline ID'), so the schema adequately documents the parameter. The description adds no additional semantic context about the parameter, earning the baseline score for high-coverage schemas.

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 'Get pipeline stages' is largely tautological, restating the tool name 'get_stages' with minimal expansion. While it confirms the domain (pipeline), it fails to distinguish this bulk-fetch tool from the sibling 'get_stage' (singular) or clarify the scope of retrieval.

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 provided on when to use this tool versus alternatives like 'get_stage' (for single stage retrieval) or 'get_pipeline'. The description does not explain what happens when the optional 'pipeline_id' parameter is omitted (e.g., returns all stages vs. error).

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