Purchase history

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

Discloses pagination behavior and read-only nature, but with no annotations, the description carries full burden. Lacks details on authentication requirements, rate limits, or error handling.

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?

Two concise sentences: first defines purpose, second explains pagination. No redundant information; every sentence serves a clear function.

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?

Adequately covers pagination mechanics, which is the main complexity. However, with no output schema and no annotations, the description could mention return format or prerequisites like authentication. Still, it is largely complete for a read-only tool with two well-documented params.

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 has 100% coverage with descriptions. The description adds the usage pattern 'start with offset 0, then pass the returned next_offset', but this is mostly a clarification of existing schema info. No significant additional meaning beyond schema.

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?

Clearly states 'Read authenticated Glovo order history' – a specific verb (Read) and resource (order history). Distinguishes from siblings like glovo_get_order_items and glovo_get_order_stats.

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?

Explains cursor-based pagination with offset and next_offset, providing clear usage context. However, no explicit guidance on when to use this tool vs. siblings or when not to use it.

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