billy_vendors

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'List' wording is consistent with those traits. The description adds little behavioral context beyond that, such as pagination, response shape, or what 'access exceptions' specifically entails, but it does not contradict the annotations.

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 focused sentence with no filler or repetition. It front-loads the action ('List') and immediately names the resource and purpose, making it appropriately sized for a zero-parameter tool.

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-argument, read-only listing operation with strong annotations, the description is largely sufficient: it states what is listed and why. The main gap is that 'access exceptions' is not explained, and there is no mention of what fields or entries the list contains, but no output schema exists to fill that gap.

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?

The input schema has zero properties, so there are no parameters to document or clarify. The 100% schema coverage and empty schema make parameter semantics non-issues; this is the baseline case for a no-parameter tool.

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 states a specific verb ('List') and resource ('vendor billing portals and access exceptions') and connects it to a clear use case ('for receipt retrieval'). It is specific enough to distinguish from generic siblings like billy_list, though it does not explicitly contrast itself with any sibling.

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 phrase 'for receipt retrieval' hints at when the tool is useful, but there is no explicit guidance about when to use this tool versus alternatives such as billy_list, billy_receipts, or billy_save_vendor. No exclusions or decision rules are provided.

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