list_bills

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

With no annotations provided, the description carries the behavioral disclosure burden. It reveals meaningful behavior: query is case-insensitive substring matching against specific fields, limit is capped at 200, offset enables paging, and total_matching reflects all matches. This goes well beyond what the schema alone communicates.

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 three compact sentences with no filler. It front-loads the main purpose, then adds parameter and pagination details, with every sentence contributing useful information.

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 list tool with an output schema, the description covers search behavior, pagination, and result-count semantics well. Minor gaps remain, such as explicit guidance on obtaining session_code and sort order, but these are partially addressed by sibling tools and the output schema.

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 real meaning for query, limit, and offset by defining matching semantics and pagination behavior. However, it does not explain session_code beyond the phrase 'in a session,' even though it is the only required parameter.

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 opens with 'List bills in a session, optionally filtered by a search term,' which names a specific verb, resource, and scope. This clearly distinguishes it from singular tools like get_bill and from list_sessions.

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 for when to use the tool: listing bills within a session, with optional filtering and pagination. It does not explicitly name alternatives or exclusion cases, but the context is sufficient to avoid confusion with sibling tools.

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