fetch_realtime_pricing

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

Discloses no authentication required, automatic BYOL detection, specific SKU counts, and inclusion of summary statistics. Annotations already declare readOnlyHint and idempotentHint; description adds valuable behavioral context beyond that.

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 concise sentences, front-loaded with main action, no redundancy. Every sentence provides distinct value (what it does, what it returns, access requirements).

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 three optional parameters, no output schema, and numerous sibling tools, the description covers core behavior and output. Could mention filtering effects of category/search parameters for full completeness, but adequate for real-time pricing fetch.

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% and parameters are well-described in the schema. Description does not add additional meaning or context about the parameters (currency, category, search) beyond what schema provides.

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?

Clearly states 'Fetch real-time pricing' with specific details: returns 592 SKUs, PAY_AS_YOU_GO pricing, auto-detects BYOL. Distinguishes from sibling tools like get_pricing or calculate_monthly_cost by emphasizing real-time nature and no authentication.

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?

Implies use for real-time pricing scenarios but does not explicitly state when to use this tool versus alternatives like get_pricing (historical) or calculate_monthly_cost (aggregated costs). No when-not or exclusion criteria.

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