cloud_get_pricing

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

The description adds 'Read only, free' and 'Compact by default' beyond the schema, indicating safe read behavior and default view. However, it omits details about pagination, response structure, or any side effects, which is acceptable given no 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?

Three short sentences with front-loaded purpose. Every sentence adds value: the first states purpose, the second adds behavioral traits, the third explains default view. No wasted words.

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?

With no output schema and 3 parameters, the description lacks explanation of response structure (list vs single item) and filtering via query. The 'compact by default' is helpful but incomplete for an agent to fully understand the tool's behavior without additional 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?

Schema coverage is 100%, so baseline 3. The description adds 'Compact by default' which clarifies the verbose parameter's default, but otherwise adds little meaning beyond the schema's parameter descriptions.

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 'Get full pricing for the account currency' with a clear verb and resource. It distinguishes from sibling list tools by focusing on pricing, but does not clarify whether it returns a list or single item, leaving some ambiguity.

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 guidance on when to use this tool versus alternatives. The description implies it's for retrieving pricing but does not specify context or exclude other uses.

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