get_all_cart_transforms

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions fetching all including inactive, but fails to disclose pagination behavior (despite the 'after' and 'first' parameters), default return format, or whether the call is read-only. The term 'all' is misleading given pagination parameters exist, suggesting it may not actually return all results in a single response.

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 a single, concise sentence that front-loads the primary purpose. It contains no fluff or redundant information, earning a perfect score for conciseness.

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?

The tool has no output schema and no annotations, so the description should compensate by explaining what is returned and any important behaviors. It only states the fetch scope, omitting details about response structure, pagination, or how 'all' interacts with the 'first' parameter. This leaves the agent with insufficient context to use the tool correctly for complex scenarios.

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%, with each parameter clearly documented (cursor, count, includeInactive). The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 clearly states the tool fetches all cart transforms, including inactive ones. This distinguishes it from sibling tool get_cart_transforms, which likely returns a filtered or default set. The verb 'Fetch' and resource 'cart transforms' are specific and unambiguous.

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 implies this tool is for retrieving the complete set of cart transforms, including inactive ones, but does not explicitly state when to use this over get_cart_transforms or other alternatives. There are no exclusion criteria or scenario-based guidance, so usage is only implied.

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