get_bill

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds no behavioral context—it doesn't mention what happens if the ID is not found, what data the response contains, or any other runtime behavior. It contributes zero value beyond 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 severely under-specified, consisting of only two words. While it is not verbose, the extreme brevity omits necessary context and fails to be appropriately sized. It provides no useful information beyond the tool name.

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 simple get-by-id tool with no output schema, the description should at least mention that it retrieves a bill resource, but it doesn't. The combination of name, schema, and annotations provides minimal context, but the description itself fails to be complete enough to help an agent understand the return value or distinguish it from siblings.

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 100% coverage: the only parameter, 'id', is described as 'id of Bill to retrieve'. The tool description adds no additional parameter semantics, but the baseline is set at 3 for high schema coverage, so this is acceptable.

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 "Get Bill" is a tautology—it restates the tool name (get_bill) verbatim without adding a specific verb+resource context. It does not distinguish from sibling get_* tools like get_invoice or get_order, offering no clarity on what a 'bill' is or how this operation differs from list_bills.

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?

No usage guidance is provided. The description does not state when to use this tool versus alternatives, lacks any mention of prerequisites or filtering, and omits mention that it retrieves a single bill by ID. There is no context to help an agent choose this over list_bills or search-related tools.

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