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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds a meaningful behavioral note: 'No human approval is conferred', which is not in annotations and clarifies a limitation. This is useful context beyond what structured fields provide.

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 two sentences with no redundancy. The core action and subject are front-loaded, and the additional note about obsolescence and approval is concise. Every word adds value without padding.

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 simple read tool with one parameter and no output schema, the description sufficiently conveys what is returned (report, revision, mappings) and the crucial caveat about approval. It does not detail return format or error scenarios, but given the tool's simplicity, this is a minor gap. The description is complete enough for an agent to call it correctly.

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?

The input schema fully documents projectId with format, length, and a clear description, so schema coverage is 100%. The tool description does not add any parameter-specific meaning; it focuses on the action, not the parameter. Given the high schema coverage, a baseline score of 3 is appropriate.

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 clearly states a specific action (read) on a specific resource (latest stored business check report) and includes details about revision and field mappings. It distinguishes this tool from generic read tools by specifying it retrieves the latest report and its mappings, making its purpose unmistakable.

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?

The description implies a usage context with 'An obsolete report requires rechecking', suggesting when this tool might be insufficient, but does not explicitly guide when to use this tool versus alternatives like helvabase_check_draft or other read tools. No exclusions or alternative tool names are provided, leaving the choice somewhat to inference.

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