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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The one added sentence about MCP approval requirements and business workflow approvals is vague and never explains how approvals affect a read operation, so it adds minimal usable behavioral context.

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 core instruction is front-loaded and short, but the trailing approvals sentence is filler for a read tool and dilutes focus. Two of three sentences are generic boilerplate rather than tool-specific guidance.

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?

With an output schema present and rich annotations, the description only needs to nail selection guidance and the identifier semantics. It fails on both: no differentiation from list/impact siblings and no explanation of the id, leaving the overall definition merely adequate.

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%, but the single parameter is fully constrained in the schema by type, uuid format, and a strict regex pattern. The description adds nothing about what a changeRequestId refers to or how to obtain one, so it neither compensates for nor badly needs the coverage gap.

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 and resource ('Read a change request') and scopes it to RetailHardHat change_requests in the connected organization, which distinguishes it from create/update/delete variants. It does not distinguish it from the closer siblings list_change_requests or get_change_request_budget_impact.

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?

'Use this when working with RetailHardHat change_requests records' is a context statement, not a when-to-use rule, and no alternative is named. An agent deciding between this, list_change_requests, and get_change_request_budget_impact gets no routing help.

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