list_expenses

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It accurately conveys that this is a listing operation with optional filters, but it does not mention ordering, pagination, authentication requirements, or what the returned expense objects look like.

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 a single sentence with no filler. It front-loads the core operation ('List expenses') and immediately follows with the relevant optional filtering semantics.

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 simple list tool with two optional parameters and no output schema, the description covers the essential call semantics. However, it does not explain return shape, sorting, or how to choose between this and monthly_summary/list_categories, leaving some selection context to the agent.

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 0%, so the description must compensate. It adds the expected month format (YYYY-MM) and clarifies that filters are optional and combinable via 'and/or', but it gives no useful meaning for 'category' beyond the raw property name—such as valid values or where categories come from.

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 uses a specific verb ('List') and resource ('expenses') and clarifies the optional month/category filters. It is reasonably distinguishable from siblings like monthly_summary and list_categories by the resource named, though it does not explicitly contrast itself with them.

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 gives clear context that this tool lists item-level expenses and can be filtered, so an agent can infer when it applies. However, it provides no explicit guidance on when to prefer list_expenses over monthly_summary or list_categories, leaving alternative selection to inference.

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