list_expenses

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

The description simply states the listing action without disclosing behavioral traits such as read-only nature, pagination, rate limits, or authentication requirements. Since no annotations are provided, the description carries the full burden and is insufficient.

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?

A single, clear sentence with no unnecessary words or repetition. It is as concise as possible while conveying the core purpose.

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?

The description is minimal and does not address return value shape, ordering, pagination, or error cases. Given low complexity and no output schema, more context would be needed for an agent to use the tool correctly.

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 0%, and the description does not add details about parameter format, types, or constraints beyond implying the date range. The phrase 'inclusive date range' gives some context but does not compensate for the lack of schema descriptions.

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 states 'List expense entries within an inclusive date range', with a clear verb ('List') and resource ('expense entries'), and a specific constraint (date range). It distinguishes well from siblings 'add_expense' and 'summarize'.

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?

No guidance on when to use this tool versus alternatives. The description lacks any explicit when-to-use or when-not-to-use statements, and does not mention sibling tools.

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