list_transactions

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

Annotations already indicate readOnlyHint=true. The description adds that many private deals are undisclosed and lists the fields returned, which helps set expectations. No contradictions.

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?

Front-loaded with the tool's purpose and scope, followed by a list of returned fields, filters, example, and exclusions. Could be slightly more concise but efficient overall.

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?

No output schema, but description outlines return fields. However, it fails to document all 10 parameters comprehensively; some filter descriptions are missing and there's an inconsistency with the 'year' parameter. For a tool with many parameters, more complete parameter guidance is needed.

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 has 0% parameter descriptions. The description mentions several filters (year, min_value_usd, region, buyer, target) but omits others like seller, deal_type, max_value_usd, date ranges, limit, offset. Incorrectly references 'year' which is not in schema, causing potential confusion. Adds some value but incomplete.

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 it lists M&A and capital transactions in the data center sector, detailing the number of deals, time range, and returned fields. It distinguishes from sibling tools hyperscaler_deals and deal_autopsy, ensuring the agent knows when to use this tool.

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?

Explicitly provides usage context: 'Broad M&A and capital-deal flow with filters; do NOT use for hyperscaler-specific... (use hyperscaler_deals) or a single-deal post-mortem (use deal_autopsy).' Also includes an example invocation with parameters.

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