process_order

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'error handling' abstractly but gives no specifics on side effects, authorization needs, or return behavior, leaving the agent uninformed about safety or consequences.

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 very short, but it is not effective conciseness; it wastes space on meta-commentary ('Demonstrates a tool...') instead of providing functional information. Every sentence should earn its place.

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?

Given no output schema, no annotations, and a tool that likely creates or modifies data, the description is completely inadequate. It does not mention return values, potential errors, prerequisites, or any operational context.

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 high (75% or more), so the baseline is 3. The description adds no extra meaning beyond what the schema already provides; it only notes the schema is 'rich' without clarifying parameter roles or constraints.

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 'Demonstrates a tool with a rich input schema' fails to state the tool's actual function; it is a tautology about schema characteristics rather than specifying the action or resource (e.g., 'process an order').

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?

No guidance is provided on when to use this tool versus alternatives like 'fetch_data' or 'manage_file'; the description is entirely meta and does not indicate context or exclusions.

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