list_billterms

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

Beyond the readOnlyHint annotation, the description discloses detailed behavioral traits: the leading 'Showing X-Y of Z billterms' line, the compact one-line-per-term default, the count-only effect of limit=0, and the structured JSON fields available with verbose=true. This gives an agent a strong model of the tool's runtime behavior.

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-organized: a one-line purpose, then output behavior, then paging guidance, then detailed args. Every sentence adds operational value, and the most important information is front-loaded before the Args section.

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 tool with an output schema, the description covers purpose, output shape, paging, count-mode, and verbose-mode tradeoffs. All three optional parameters are explained, and no critical detail needed to invoke the tool correctly is missing.

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 fully compensates by explaining every parameter: verbose (with concrete use cases), limit (default, max, and the special 0=count-only behavior), and offset (0-indexed, default 0). This exceeds what the bare schema provides and leaves no parameter ambiguous.

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 all billing terms,' a specific verb and resource, and clearly differentiates from siblings like create_billterm and list_taxtables. The scope ('all billing terms') and multiple output formats are stated unambiguously.

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 on when to use default compact output versus verbose JSON, and how to use limit/offset for paging. It doesn't explicitly name alternative tools or when-not-to-use conditions, but for a read-only list operation this is sufficient and unambiguous.

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