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

Annotations already declare write semantics (readOnlyHint=false), idempotency and non-destructiveness. The description adds two things beyond them: implied optimistic concurrency ('with its current version') and the semantic limitation that a recorded decision is not proof of resolution. It omits failure behavior on version mismatch and any permission requirements, keeping it at an adequate 3.

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 tight sentences with the action front-loaded and the semantic caveat placed last where it belongs. No filler; minor crypticness in 'Explicitly' and 'Never proves technical resolution' costs the top band.

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?

A mutation tool with no output schema, a nested object argument, and zero schema description coverage. The description conveys the core intent and the versioning requirement, but leaves the identity/scope parameters and error behavior undocumented, which is thin for a write tool.

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. It names disposition, note, owner and follow-up date, covering four of the six nested fields, and hints at expectedVersion via 'with its current version', but says nothing about id or applicationIds. Partial compensation only.

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 and resource: recording a finding disposition, note, owner or follow-up date, with the added 'with its current version' versioning qualifier. It does not name or contrast with any sibling (grant_question, verify_facts, check_coverage), so an agent cannot route on the description alone, but the action itself is clear.

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?

No when-to-use guidance and no alternatives named despite many siblings (verify_facts, check_coverage, grant_question). 'Never proves technical resolution' is a semantic caveat, not routing guidance, so the agent is left to infer when a recorded decision is the right call versus verification tools.

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