billy_list_payment_terms_modes

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

The description includes 'READ-ONLY', explicitly disclosing that the tool does not modify data. Since no annotations are provided, this behavioral hint is valuable. It does not cover other aspects like rate limits, but for a simple list tool, this is adequate.

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 extremely concise at two sentences, front-loading the purpose and adding the behavioral note. Every word is meaningful with no redundancy.

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 zero-parameter list tool, the description is complete. It specifies the resource and the read-only nature. No output schema or additional context is necessary, and the sibling tools do not overlap.

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?

There are zero parameters, and the schema is empty with 100% coverage. According to guidelines, 0 parameters yields a baseline of 4. The description adds no parameter information, but it is not required.

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 the verb 'List' and the resource 'payment-terms modes', making the purpose unambiguous. It distinguishes itself from sibling list tools by specifying a unique resource, and there are no other tools with similar names.

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 provides no explicit guidance on when to use this tool versus alternatives. While the tool's purpose is clear, it does not mention contexts where it is preferred or excluded, leaving the agent to infer from the name alone.

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