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 elsewhere. The description adds only content shape per view; it says nothing about pagination behavior despite an offset parameter with a 1,000,000 ceiling, nothing about defaults, and nothing about auth or rate limits.

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?

It is one long run-on sentence built from nested parentheticals, with no front-loaded statement of what the tool is for. The information is dense but the structure forces the reader to parse five parenthetical blocks to find the purpose.

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 shape need not be described, and the per-view contents are a reasonable supplement. Still, for a 6-parameter, 0%-schema-coverage tool with paging, the missing explanation of offset and of the match/state enum semantics leaves real gaps.

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 must carry the load, and it does explain all five 'view' values plus the YYYY-MM format for period. But it only gestures at 'match filters' and 'state filters' without explaining the enum meanings, and never mentions offset or its paging role.

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 sentence names the resource ('agent spend') and enumerates the five views it can render, so an agent can infer what the tool returns. However, the framing verb is just 'view' and the whole thing is a parameter enumeration rather than a purpose statement, and nothing distinguishes it from close siblings like check_agent_spend, coding_agent_spend, agent_action, or agent_approvals.

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?

Each view is given a short gloss of its contents ('one agent: mandate, cards, latest transactions...', 'the month's agent spend controls report for the close and the auditor'), which implicitly tells the agent which view to pick. There is no explicit when-not guidance and no routing to the sibling tools that cover overlapping agent-spend territory.

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