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

Annotations already declare readOnlyHint=true, covering the read-only safety profile. The description adds the endpoint (GET /transactions) and filter context, which aligns with the annotations. No additional behavioral traits beyond what annotations provide are needed, achieving a score of 4.

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 plus the endpoint, highly concise. It front-loads the core purpose ('List/search payment transactions') and wastes no words.

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 13 parameters all described in the schema, no output schema, and readOnlyHint, the description is adequate. However, it could briefly mention pagination (startingAfter) or ordering, but not required for completeness given the schema coverage.

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%, so the baseline is 3. The description only lists generic filter categories ('entity, invoice, status, type and date') without adding meaning beyond what the schema already details for each parameter.

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 tool lists/searches payment transactions, mentions key filters (entity, invoice, status, type, date), and includes the endpoint. This distinguishes it from siblings like get_transaction (single transaction) and find_invoices (invoices vs 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 description implies search functionality but does not explicitly state when to use this tool over alternatives like get_transaction or find_invoices. No when-not or exclusion criteria are provided, limiting guidance for an AI agent.

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