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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the tool produces counts and examples, but it does not disclose additional behavioral traits such as data freshness, scope limitations, or response shape beyond what the prose already implies.

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 description is a single sentence that front-loads the main purpose ('Summarize accounting problems that need review') and then lists the essential output details. Every phrase earns its place, with no filler or redundant restatement of the tool name.

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 no output schema, the description adequately communicates the return contents: counts for three transaction categories and examples of two of them. It is slightly incomplete because it does not describe the response structure or behavior for edge cases like no issues, but for a simple summary tool it provides the core information an agent needs.

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 100%, and both parameters have clear descriptions ('Portfolio exact name or slug', 'Workspace exact name or slug'). The tool description does not add parameter-level meaning, but it does not need to because the schema already fully documents them. Baseline 3 is appropriate.

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 ('Summarize'), a resource ('accounting problems that need review'), and concrete output contents ('exact counts for uncategorized, errored, and spam-related transactions, plus examples'). It clearly distinguishes itself from other getter/list tools by focusing on an issue summary rather than balances, positions, or individual transactions.

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 'accounting problems that need review' gives a clear context for when to use this tool: when an agent needs an overview of problematic transactions. It does not explicitly name alternatives or state when not to use it, so it falls short of an explicit when/when-not guide.

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