calculate_viewport_responsive

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It usefully mentions the 0.005 USDC Base L2 fee, but it does not disclose whether paymentSignature is required, what the output looks like, or whether there are side effects beyond the fee.

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 two short sentences with no filler. The core operation and audience are front-loaded, and the pricing detail earns its place as actionable context.

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 a generic 'payload' parameter and no output schema, the agent still lacks a concrete input contract and return format. The description is enough for tool selection but not enough for confident invocation without additional guessing.

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 baseline is 3. The description adds domain hints about viewport/breakpoints and Base L2 payment, but it does not explain the expected payload structure beyond what the schema already says.

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 uses a precise verb, 'Generates,' and a specific artifact: 'responsive viewport breakpoint media query matrices.' The audience qualifier 'for web generation agents' and the unique domain clearly distinguish it from the large field of sibling tools.

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 only usage context is the target audience ('for web generation agents') and a pricing note. There is no explicit 'use when' or 'use instead' guidance, though the absence of a close sibling tool makes the implied context somewhat useful.

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