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

Annotations already declare readOnlyHint=true, and the description complements this with 'Paginated' and 'Harvest REST: GET /expenses,' reinforcing the non-mutating GET nature. It does not disclose rate limits, auth requirements, or return envelope, but the read-only annotation lowers the burden; this is adequate but minimal.

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 two short sentences, each adding value: the first states the action and filter options, the second notes pagination and the REST endpoint. No filler or redundant elaboration.

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 operation, the description covers the core capabilities: filtering across all major dimensions, pagination, and the backing REST call. It omits the exact response structure (likely an array of expenses), but given there is no output schema and the annotation already marks it read-only, the description provides sufficient context for selection and basic invocation.

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?

All 9 parameters have descriptions in the schema, so the schema coverage is 100%. The description's phrase 'filtered by user, client, project, date range, billed status, or updated-since' summarizes the filter parameters, but adds no new meaning beyond the field-level schema documentation. Baseline 3 applies.

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?

Description opens with 'List expenses,' a clear verb+resource pair, and enumerates optional filters (user, client, project, date range, billed status, updated-since). It is easily distinguished from sibling list tools like list_projects or list_clients by the expense resource.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or fallback tools. Usage must be inferred from the plural 'List expenses' and the pagination note; there's no guidance like 'use this when retrieving expense records.'

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