Get the Woolworths trolley

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

The description details the response shape (`lines`, `lineCount`, `totalQuantity`, `totals`) and explains aggregation semantics with a concrete example of 19 lines summing to 23 items. It also discloses the authentication requirement, complementing the readOnlyHint annotation without contradicting it.

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?

Every sentence contributes: purpose, return payload semantics, and the session prerequisite. It is compact, front-loaded, and free of filler.

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?

For a zero-parameter read-only tool with no output schema, the description fully compensates by enumerating the return fields and their meaning, plus the login prerequisite. Nothing needed for correct invocation is missing.

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 has no parameters, so the empty schema fully covers this dimension. With zero parameters, the baseline is 4; there is nothing more the description could add about parameter usage.

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 opens with 'List the trolley,' a specific verb and resource, and then elaborates on the exact returned fields. It is unmistakably about reading the current cart, separate from product search or cart mutation siblings.

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?

It clearly states the key precondition for use: a signed-in session, with concrete instructions to run `npm run login` or call sign_in. It does not explicitly name alternative tools, but the purpose and prerequisite strongly frame when this tool is appropriate.

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