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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: results are newest-first, scope is limited to the signed-in person's own records, and no extra identifying details are required. It omits pagination/limit behavior, which is a real gap for a list tool.

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 dense sentences with the core purpose and scope front-loaded, followed by filter semantics. Tight overall, though the trailing 'Needs no details from the person beyond what to look for' is slightly padded phrasing for a simple no-extraneous-input point.

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 no output schema, the description usefully conveys record shape (income/expense records, newest first) and the review-queue concept. For a 7-parameter list endpoint it would be stronger if it mentioned the result cap (limit default 25, max 100) or how to page through more than the default.

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 does for the key ambiguous params: needsReview is explained as 'still waiting for a business-or-personal decision (the review queue)' and type/taxYear/search are described in prose. The limit parameter and its default/cap are not addressed.

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 and resource ('Read and search the signed-in person's own income and expense records in their TapTax account') plus the result ordering ('newest first'). This clearly separates it from add_transaction, update_transaction, and the invoice tools in the sibling list.

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?

Explains the available filter axes and points to a concrete use case ('needsReview=true ... the review queue'), giving clear context for when to reach for it. It never names an alternative tool or states exclusions, so it stops short of the top score.

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