list_strategies

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which the description does not contradict. The description adds context that this tool lists strategies for an application, which is consistent. No extra behavioral details are provided, but annotations cover the main concerns, so a 4 is appropriate.

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 a single, concise sentence that conveys the tool's purpose without wasted words. It is front-loaded with the action and resource.

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 list tool with one required parameter, annotations cover read-only and idempotent behaviors. The output is not described, but with no output schema, a brief mention of expected return (e.g., list of strategy names) could improve completeness. However, given low complexity, it is nearly complete.

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?

The input schema has 100% coverage with description for the 'application' parameter: 'Application name as registered in Spinnaker'. This is clear and sufficient. The description does not add parameter details beyond what the schema provides, but the schema itself is rich enough. Baseline 3.

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 'List all deployment strategies configured for a Spinnaker application', using a specific verb ('list'), resource ('deployment strategies'), and context ('for a Spinnaker application'). This distinguishes it from sibling tools like 'list_pipelines' or 'delete_strategy'.

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 strategies, but does not explicitly mention when to use this over alternatives or any limitations. With siblings like 'save_strategy' and 'delete_strategy', it would benefit from guidance on when to list vs. other operations.

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