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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=true, so the agent knows this is a non-idempotent mutation. The description adds only '(rebuild)' as behavioral color; it does not say what happens to the in-flight run, whether it supersedes an existing run, or what side effects follow. Annotations carry most of the weight here, so a 3 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?

Two short sentences, zero filler, with the action stated first and the prerequisite second. Every clause earns its place.

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 low-complexity, two-parameter tool with no output schema and annotations covering the safety profile, the description tells the agent what it does and where to get the required id. It omits run-state preconditions (e.g., whether the run must be finished or failed), which is the only meaningful remaining gap.

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 coverage is 100% and both parameters are self-describing ('workflow run id to rerun', 'Application's id'), so the schema does the heavy lifting. The description adds only the provenance hint that run_id comes from list_application_workflow_runs, which is a modest value-add rather than new semantics.

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?

States a specific verb and resource — 'Rerun one of an Application's CI/CD workflow runs' — with the '(rebuild)' gloss disambiguating it from a plain restart. It names the companion list tool but does not distinguish itself from adjacent siblings like retry_application or watch_workflow_run, so it stops short of full differentiation.

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?

'Use list_application_workflow_runs to find the run id' gives a concrete prerequisite, which is real procedural guidance. However, there is no statement of when to choose this over retry_application, retry_execution, or watch_workflow_run, and no exclusion conditions (e.g., run must be completed/failed).

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