get_pending_orders

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

The description states 'gets' which implies a read-only operation, but annotations indicate destructiveHint=true and readOnlyHint=false, contradicting that implication. The description fails to disclose that the tool may have side effects, making it misleading.

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 a single sentence that is concise and front-loaded. It contains no unnecessary information, but the conciseness is undermined by the contradiction with annotations.

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 the annotations suggesting destructive behavior and no output schema, the description is severely incomplete. It does not explain the side effects, return format, or any other context needed to use the tool correctly.

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 has no parameters, so the description does not need to clarify parameter usage. With zero parameters, baseline is 4, and the description does not add but also does not detract.

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 'Gets all orders with pending status' clearly identifies the verb (gets), resource (orders), and filter (pending status). It is specific and distinct from sibling tools like 'get_daily_sales' or 'query_database'.

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 on when to use this tool versus alternatives. There is no mention of prerequisites, limitations, or when not to use it. The agent receives no help in selecting between this and other data retrieval tools.

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