list_billterms

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

With no annotations provided, the description carries full responsibility. It discloses the leading 'Showing X-Y of Z billterms' summary line, the default compact format vs verbose output, pagination behavior, and the count-only mode via limit=0. This is meaningful behavioral context beyond what a schema alone would convey.

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 well-structured: a one-sentence purpose, a behavior overview paragraph, and a clean Args section. Every sentence earns its place with concrete details (defaults, max, special values) and zero filler.

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 present, the description covers the key user-facing behaviors: output format, pagination, count-only, and verbosity control. It doesn't need to describe return values since an output schema exists. Minor gap: doesn't mention max 250 limit in the Args section vs overview, but the overview-carrying version is present.

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%, so the description must compensate entirely. It explains all three parameters: verbose (full JSON vs compact), limit (page size, default 50, max 250, 0=count only), and offset (0-indexed first row). This goes well beyond what the raw schema types/defaults convey.

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 clearly states 'List all billing terms' with a specific verb and resource. It distinguishes itself from siblings by describing the compact output format and verbose option, which is unique to this listing tool.

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 explains the default output format ('one-line-per-term format by default'), how to page with offset, use limit=0 for count-only, and when to use verbose=true for full JSON. It gives clear context on invocation options but doesn't explicitly name alternative tools or when not to use it, which is acceptable for a list operation.

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