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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured fields. The description adds a modest amount of context about the two approval layers (admin-configurable MCP requirements vs. always-applicable business workflow approvals), but does not say what happens when no approval request exists for the invoice.

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 core action. The second sentence is somewhat tangential to invocation and slightly awkwardly worded ('a invoice'), but it is not 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?

Output schema exists, so return values need not be described, and annotations cover the safety profile. The remaining gap is the unresolved find-vs-get ambiguity among siblings and the absent explanation of the single required identifier, which is what an agent most needs before calling.

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 carries the burden, and it only implies the semantics: looking up a request 'for a invoice' tells the agent that entityId is an invoice identifier. It never names entityId or acknowledges entityType, though the schema's const 'invoice' and UUID pattern make those largely self-explanatory.

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?

States a specific verb and resource: 'Read the existing business approval request for a invoice.' This is clearly distinguishable from submit/cancel/decide_invoice_approval_request, but it does not explain how it relates to get_invoice_approval_request, the closest sibling whose name and purpose overlap almost entirely.

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 is given. The second sentence discusses how approval requirements are configured, which is background about the data, not about when to call this tool rather than get_invoice_approval_request, list_pending_approval_requests, or get_approval_status.

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