list_transactions

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

With no annotations, the description must disclose behavioral traits fully. Instead, it introduces an incongruent behavior ('Read sample CSV') and fails to mention side effects, data source, or handling of validation failures. The description actively misleads about what the tool does.

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 short sentence, but it is not appropriately concise because it omits essential information and substitutes misleading details. It is under-specified rather than efficiently structured.

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?

Despite having an output schema, the description is completely inadequate. It fails to explain the actual operation, prerequisites, or relation to the input parameters, leaving the tool's behavior entirely ambiguous and inconsistent with its name and schema.

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?

Although schema descriptions cover 100% of parameters, the tool description adds no value and actually contradicts the parameters by referencing CSV instead of account_id and date ranges. The agent cannot infer how parameters relate to the described CSV processing.

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 'Read sample CSV, normalize rows → Transaction[] with schema validation' does not match the tool name 'list_transactions' or its parameters (account_id, start_date, end_date). It describes a CSV processing operation instead of listing transactions, making it misleading about the tool's actual purpose.

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 description provides no guidance on when to use this tool versus alternatives like get_transactions. It does not mention the intended use case (e.g., fetching transactions for an account within a date range), leaving the agent without context for selection.

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