Get Cart Limits

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond them: null limits mean increases are disabled until both limits are set locally, tools cannot raise or disable limits, and unknown item prices block increases — all non-obvious constraints for an agent reasoning about cart operations.

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?

Four short sentences, front-loaded with what is returned before the constraint notes. All sentences carry information, though the phrasing of 'Null limits means increases are disabled until both limits are set by the user locally' is slightly awkward and could be tightened.

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?

An output schema exists, so return values need not be explained. For a zero-parameter read tool with annotations covering the safety profile, the description supplies everything else needed: the semantics of a null result and the conditions that block cart increases.

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 takes zero parameters, so the baseline is 4 per the rubric. Schema coverage is 100% and there is nothing for the description to disambiguate about inputs.

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?

States a precise verb+resource ('Return locally configured maximum merchandise rials and total units') and narrows the scope with 'excluding shipping' and 'locally configured'. An agent can tell this reads cart-level increase limits rather than any sibling cart mutation tool such as add_to_cart or read_cart.

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?

Usage is only implied: the mention that 'unknown item prices block increases' and 'tools cannot raise or disable these limits' hints this is a pre-flight check before a cart increase, but the description never explicitly says when to call it versus prepare_cart_change or add_to_cart. No exclusions or alternatives are named.

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