Reconcile application

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

The description adds meaningful behavioral context beyond the annotations: it discloses the read-confirm-poll workflow, that the operation is queued and asynchronous, and that applications:manage plus a client-global idempotency key are required. Annotations already cover destructiveHint, idempotentHint, and openWorldHint, so the remaining gap is that it does not spell out exactly what reconciliation changes or risks.

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 three tight sentences and front-loads the purpose before moving to workflow and prerequisites. Every sentence contributes distinct information with no wasted wording.

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 four required parameters, no output schema, and rich annotations, the description is complete enough for correct invocation. It covers purpose, required scope, idempotency handling, confirmation, and the polling behavior needed after the queued operation completes.

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 100%, so the schema already documents all four parameters in detail. The description only echoes the idempotency key requirement and does not add syntax or format guidance beyond the schema, which matches the baseline 3 for high schema coverage.

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 states a specific verb and resource: 'Reconcile an owned managed application with its declared configuration.' This is clearer than a bare verb, but it does not explicitly distinguish the tool from related application lifecycle siblings such as repair_application, update_application, or rollback_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?

It gives a clear operational sequence: read the installation first, confirm the action, then poll installation and events until the queued operation completes. It also names required permission and idempotency key prerequisites. However, it does not name alternatives or state when this should be chosen over repair_application or update_application.

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