pending_orders

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

With no annotations, the description carries the burden of behavioral disclosure, and it does state 'Read-only' directly. It also explains the inclusion/exclusion semantics of the result set. It could add more about return shape or ordering, but for a simple listing tool this is solid.

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?

Four concise sentences with no filler. The tool's identity and scope are front-loaded, and each sentence adds meaningful information: contents, source, exclusions, and read-only behavior.

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 queue listing, the description covers what it contains, where web rows come from, what is excluded, which sibling to use instead, and that it is read-only. Nothing essential is missing for correct selection and 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?

The input schema has zero parameters and 100% schema coverage, so the baseline is 4. No parameter-level description is needed because there is nothing to invoke with.

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 clearly defines what the tool exposes: a Pending Order queue of counter and dealer rows for submitted firearm shipments needing disposal, payment, or a ShipStation push. It also distinguishes itself from related sources by explicitly stating web-shop rows come from pending_web_orders and consignment fulfillment is excluded.

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 gives explicit routing guidance: consignment fulfillment is NOT here and belongs in consignment_queue, while web-shop rows belong to pending_web_orders. This tells an agent when to use this tool versus its key siblings.

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