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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds useful ordering context ('newest first') and explains what needsReview=true represents (the review queue). It does not disclose pagination behavior or default ordering interaction with limit.

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?

Two sentences, front-loaded with the action and scope, then the filter options. No filler and every clause adds information.

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 read-only list tool with no output schema, the description covers what is retrieved, ordering, and the filter semantics that matter most. It is slightly thin on default result size/pagination, but annotations carry the safety profile and the filter list is complete.

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 only 43%, so the description must compensate, and it partly does by naming the filter dimensions (tax year, dates, type, description text, needsReview) and clarifying that needsReview means 'still waiting for a business-or-personal decision'. However, limit, the enum values, and default value semantics are left to the schema, leaving gaps in the 7-parameter set.

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?

States a specific verb (search) and resource (income/expense transactions) scoped to the signed-in person, and explicitly distinguishes itself from the mutation siblings (add_transaction, update_transaction) via the read-only 'signed-in person's' framing. An agent can identify this as the read/list counterpart to the write tools without opening a schema.

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?

Gives clear conditions for using it: filter by tax year, dates, type, text, or needsReview=true for the review queue. It implicitly routes agents needing to add or modify transactions to siblings, though it does not name them explicitly or state when NOT to use it.

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