orders

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It reveals nothing about side effects, permissions, output format, or the meaning of parameters like save_to_file. The agent has no idea if this operation is safe to invoke or what consequences it may have.

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?

While the description is extremely brief, this is under-specification rather than conciseness. The single phrase 'Order history.' does not provide enough substance to be considered efficient; it is merely a placeholder that omits all necessary information.

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 four parameters, no output schema, and no annotations. The description is far too shallow to cover the behavioral and semantic complexity, leaving the agent without essential information for correct invocation.

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 0%, and the description does not mention any of the four parameters (days, limit, save_to_file, summary_only). The description adds no meaning beyond what bare parameter names convey, and even those names are ambiguous without further elaboration.

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 'Order history.' is a noun phrase that essentially restates the tool name 'orders' without any verb or action. It does not specify whether the tool fetches, lists, updates, or deletes order history, and provides no differentiation from sibling tools like 'deals' or '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?

The description offers no guidance on when to use this tool versus alternatives. There are no scenarios, prerequisites, or exclusions mentioned, leaving the agent without any contextual cues for tool selection.

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