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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds useful context that the result includes steps and actions and that approval requirements are organization-configurable, but it does not explain error behavior, permissions, or whether all steps are always returned.

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 purpose is front-loaded in the first sentence, and the second sentence adds concise context about approval configuration. There is a grammatical issue ('a invoice') and the second sentence is somewhat tangential, but overall it is efficient.

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 the description need not explain return values in detail, and annotations cover the safety profile. However, for a read tool that depends on a specific requestId, the description omits how to find that ID and does not clarify usage relative to the find/cancel/decide/submit siblings.

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?

There is exactly one required parameter, requestId, and schema description coverage is 0%. The description never states that requestId identifies the invoice approval request to read, nor how to obtain it. The parameter name is suggestive, but the description does little to compensate for the missing schema documentation.

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 ('Read') and resource ('invoice approval request'), and adds that it returns steps and actions. It does not explicitly differentiate from close siblings like find_invoice_approval_request or get_budget_approval_request, so it stops short of 5.

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 no explicit guidance on when to use this tool versus find_invoice_approval_request or other approval-related siblings. The closest thing to usage guidance is the note that approval requirements are configurable, which does not tell an agent when to select this read operation.

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