Get Carts

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

The annotation already declares readOnlyHint=true, so the safety profile is known. The description adds a behavioral note about the 'purchased' parameter's effect on filtering, helping the agent understand how to target abandoned carts. No contradictions.

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, front-loaded with the action and entity. Every word adds value—the second sentence directly instructs a useful filter combination.

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 is a simple filtered list operation with no required parameters. The schema fully documents all parameters, and the description provides a practical use case. The lack of an output schema is acceptable for a list tool of this nature, matching high-caliber examples.

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 input schema already documents all 7 parameters with descriptions covering 100% of the schema. The description reinforces the 'purchased' parameter's semantics with an example, but does not add new information beyond what the schema provides, so the baseline of 3 applies.

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 the specific verb 'List' with a clear resource 'shopping carts', and explicitly mentions the filtering dimensions (purchase status, lead, date). This distinguishes it from sibling tools like hyros_get_sales and hyros_get_leads, which focus on different entities.

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 gives a concrete use case (Set purchased=false to find abandoned carts for a recovery campaign), indicating when the tool is useful. However, it does not explicitly mention alternatives or exclusions, so it stops short of full when/when-not guidance.

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