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

Annotations already declare this a safe, idempotent, non-destructive read, so the bar is lower; the description still adds real context that approval requirements are organization-configurable via MCP while business workflow approvals always apply. That tells the agent the observed state may vary by org policy, which annotations cannot express.

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, both short, with the read-only scope front-loaded ahead of the policy caveat. Nothing is redundant, though the second sentence is a caveat rather than core selection 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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. For a single-parameter read tool the description is nearly complete; the main residual gap is disambiguation from get_budget_approval_request.

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 schema only supplies type/format/pattern for budgetId without prose. The description never mentions the budgetId argument at all, but with a single, self-descriptive parameter the residual ambiguity is small, so this lands at adequate rather than deficient.

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: reads a budget's approval request and progress, and explicitly rules out making a decision. That contrasts adequately with decide_budget_approval_request and cancel_budget_approval_request, though it does not distinguish this tool from the near-identically named sibling get_budget_approval_request.

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 phrase 'without making an approval decision' implies when to pick this over the decide/cancel siblings, but no alternative tool is named and no prerequisite (e.g., an approval request must already exist) is stated. Usage is inferable rather than stated.

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