Usage And Billing MCP Server

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 but fails completely. 'Get meters' doesn't indicate whether this is a read-only operation, what permissions might be required, whether it returns all meters or a filtered subset, what format the response takes, or any rate limits or constraints. The description provides zero behavioral context beyond the basic 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?

While 'Get meters' is technically concise with only two words, this represents under-specification rather than effective conciseness. The description fails to provide necessary information about what the tool does, making it inefficient rather than appropriately brief. Every word should earn its place, but here the words don't provide enough value.

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?

Given the complexity of having sibling tools with similar names (get_meter, get_products, etc.), no annotations, and no output schema, the description is completely inadequate. It doesn't explain what 'meters' are in this system, how this differs from get_meter, what the response contains, or any behavioral characteristics. For a tool in a family of similar retrieval operations, this minimal description fails to provide necessary context.

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 tool has zero parameters, and the schema description coverage is 100%, so there are no parameters requiring documentation. The description doesn't need to explain any parameters, and the absence of parameter information in the description is appropriate for a zero-parameter tool. This meets the baseline expectation for tools with no parameters.

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 meters' is a tautology that merely restates the tool name without adding any meaningful clarification. It doesn't specify what 'meters' refers to in this context or what the operation actually does. While it includes a verb ('Get'), it lacks specificity about what resource is being retrieved and provides no differentiation from sibling tools like 'get_meter' (singular).

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 absolutely no guidance on when to use this tool versus alternatives. There are multiple sibling tools with similar names (get_meter, get_products, get_product_items, etc.), but the description offers no context about when this specific tool is appropriate, what distinguishes it from get_meter, or any prerequisites for its use. This leaves the agent with no usage guidance.

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