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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so the safety profile is fully covered structurally. The description adds only that the result is 'documented checks and correction steps', which is useful output framing but no deeper behavioral context (no rate limits, prerequisites, or failure modes).

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 sentences, front-loaded with the tool's action before the valid-value lists, with no filler. The two issue lists are dense but each value is required to constrain the enum, so the length is justified.

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?

An output schema exists, so return values need no explanation, and the input mapping is covered. What is missing for a support-desk lookup tool is guidance on when this applies versus the sibling check tools and any prerequisite context about the uploaded document.

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 carry the parameter burden. It does meaningful work by mapping which issue values belong to which document (e.g. receipt_allocation/corrected_retry are Statement 3, duplicate_document/gstr2b_mismatch are Annexure B) - a cross-parameter relationship the enum lists alone do not convey. It still does not explain what each issue means.

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 clear verb+resource (get documented checks and correction steps) and scopes it to Statement 3 / Annexure B upload errors, with the valid issue categories spelled out. It does not differentiate itself from siblings like check_receipt_allocation, which overlaps with the 'receipt_allocation' issue keyword, but the core purpose is unambiguous.

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 explicit when-to-use guidance and no mention of alternatives such as check_receipt_allocation or the refund-guide tools. The issue enumeration implies the valid inputs but gives no condition for choosing this tool over its siblings.

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