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

Annotations already indicate destructiveHint=true and readOnlyHint=false, and the description's 'Regenerate' aligns with mutation. The phrase 'with idempotency metadata' adds a small amount of behavioral context beyond the annotations, but the description does not disclose what happens to the existing decision brief, whether the regeneration is reversible, or what side effects may occur.

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 with no filler, and the core action is front-loaded. It could earn a higher score if it used the saved space to add more practical guidance, but as written it is appropriately brief.

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 destructive mutation tool with no output schema and no parameter-level documentation, the description is too thin. It does not explain the regeneration behavior, overwrite semantics, retry/idempotency usage, or expected outcome, leaving the agent with insufficient context to invoke it confidently.

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 0%, so the description must compensate, but it only broadly indicates that the tool applies to 'an application' and mentions 'idempotency metadata'. It does not explain the distinct roles of request_id versus idempotency_key, nor why only application_id is required.

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 ('Regenerate') and resource ('a decision brief for an application'), which makes the core action clear. It also distinguishes implicitly from the sibling yardstick_decision_brief_read by using 'regenerate' rather than 'read', though it does not explicitly contrast the two.

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 gives no guidance about when to use this tool versus alternatives such as yardstick_decision_brief_read. It does not state conditions, prerequisites, or exclusions, leaving the agent to infer the appropriate context from the name alone.

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