save_strategy

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

Annotations indicate readOnlyHint=false and destructiveHint=false, meaning it mutates state but is not destructive. The description confirms it creates ('Save a new...'), but does not elaborate on permissions, side effects, or whether it overwrites existing configurations. Given annotations are present, a score of 3 is appropriate as the description adds minimal context beyond confirming it is a write operation.

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 sentence of 9 words, front-loading the purpose. It is concise with no waste, but could benefit from slight elaboration on the expected JSON 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 has one required parameter, no output schema, and annotations covering safety, the description is minimally adequate. However, it lacks information on the return value (e.g., confirmation message) and does not differentiate from creating other resources, leaving some gaps.

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 schema has 100% coverage with a single parameter 'strategy_json' described as 'Full strategy JSON definition'. The description adds no additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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 saves a new deployment strategy configuration to Spinnaker. It uses a specific verb ('save') and resource ('deployment strategy configuration'), but does not distinguish from sibling tools like 'save_pipeline' or 'update_pipeline', though they handle different entities.

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?

There is no guidance on when to use this tool versus alternatives like 'delete_strategy' or 'update_pipeline'. The description does not mention prerequisites or context that would help an agent decide to invoke it.

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