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

The description asserts the operation is 'idempotent' while the annotations declare idempotentHint=false, a direct contradiction about a behaviorally significant property. It also gives no information on duration, blocking behavior, or side effects on running workloads that the annotations do not already cover.

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, with the core action front-loaded before the explanatory clause. The trailing 'Safe, idempotent' claim is wasted space because it is both unverifiable from the description and in conflict with the annotations.

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 mutating convergence action with no output schema, the description says nothing about what the agent should expect afterwards, whether the call blocks, or how long convergence takes. Combined with the idempotency contradiction, an agent cannot reliably predict the call's behavior.

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?

There is a single required parameter (application_id) and schema description coverage is 100%, so the schema fully documents the input. The description adds no format, scoping, or lookup guidance beyond that, which matches the baseline for a fully covered schema.

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?

Names a specific verb (reconcile) and resource (Application) and explains what the operation actually does: re-running platform convergence for resources and pipeline wiring. That is more informative than a restatement of the name. It does not, however, differentiate from the sibling reconcile_cluster or from adjacent application lifecycle tools such as deploy_application or retry_application.

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 statement of when to reach for this tool rather than deploy_application, retry_application, or reconcile_cluster, and no prerequisites or triggers given. The agent must infer that this is a repair/drift-correction action from the single word 'convergence'.

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