billing_provider_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a read operation ('Get'), which implies no side effects, but does not disclose details like whether the provider is returned in full or partial, any error behavior (e.g., 404 if not found), or authentication requirements. It doesn't contradict annotations (none exist), but it adds minimal context beyond the verb.

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, grammatically correct sentence with no unnecessary words. It is front-loaded with the action and resource. Perfectly concise for the tool's simplicity.

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 single-parameter read tool, the description is sufficient. The schema covers the parameter fullyaine, and there is no output schema to explain. The description notes the main action and identifier. It might be slightly more helpful to mention that the provider is returned entirely or that an error is thrown if not found, but these are minor gaps given the tool's simplicity.

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 100%, so the schema documents the 'uuid' parameter as 'Provider UUID'. The description adds no further meaning beyond what the schema provides, so baseline 3 is appropriate. It doesn't enrich the parameter with format, examples, or constraints.

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 clear verb ('Get') and resource ('billing provider') with a specific identifier (UUID). It is distinct from siblings like billing_providers_list because it retrieves a single provider by UUID. However, it does not explicitly name the sibling for listing all providers, so it's clear but lacks explicit differentiation.

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 implies usage: use when you need a specific provider by UUID. It does not provide explicit when-to-use vs. alternatives, such as 'use billing_providers_list to retrieve all providers'. While the context of sibling tools suggests the distinction, the description itself offers no guidance on alternatives or when not to use it.

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