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

Annotations already declare readOnlyHint=true, so the 'Read-only' phrase adds no new information. The description does mention filtering, sorting, and pagination, which are behavioral features, but these are already evident from the schema. No additional context about defaults, limits, or caveats is provided.

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 immediately states the main action and key capabilities. It is concise and front-loaded with the most critical information, with no fluff or repetition.

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?

For a tool with 6 parameters, all nested, and 0% schema coverage, this description is far too thin. It does not explain the complex filter structure (e.g., date ranges, status enums, field filters) or provide any usage examples. The output schema exists, reducing the need for return-format explanation, but the input side is severely underdescribed.

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?

With schema description coverage at 0%, the description must compensate for undocumented parameters. It only vaguely mentions 'filtering, sorting, and pagination' without explaining the exact filter fields, their structure, or how to combine them. This is insufficient for an agent to construct valid filter objects correctly.

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 clearly states the verb (List) and resource (transactions) and mentions filtering, sorting, and pagination. It distinguishes from transaction_get_transaction (single) but does not name any alternative, so it doesn't fully contrast with siblings. Still, the purpose is unambiguous.

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?

There is no guidance on when to use this tool versus alternatives like transaction_get_transaction or transaction_get_summary. It does not mention exclusions or conditions. The description is purely descriptive, not prescriptive.

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