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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context at all — no pagination semantics despite the cursor parameter, no default-page-size note, no indication of result ordering or volume.

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?

It is a single short clause with no wasted words, but the brevity comes from under-specification rather than efficient front-loading. There is no lead sentence stating the operation.

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 4 optional parameters, no output schema, and no description of pagination or filtering, the definition leaves the agent guessing on how to page and how filters combine. Naming the returned fields is a partial substitute for a missing output schema, but it does not cover the gaps.

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 coverage is 75%, so the baseline is 3. The description lightly maps to the project filter ('project') but does not explain limit, cursor or search behavior, and most of the listed terms (amount, vendor, cost type) are return fields rather than parameters.

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 text is a noun phrase fragment — 'Expenses with amount, date, vendor, project, cost type and who paid' — that enumerates attributes but never states an action. The verb 'list' exists only in the tool name, and nothing distinguishes this from get_expense or the many sibling list_* tools beyond the resource word.

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?

There is no when-to-use guidance, no mention of get_expense as the alternative for a single record, and no indication of what the filters are for. The agent must infer from the schema that project_id and search narrow results.

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