get_tcgplayer_orders

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb 'Get' implies a read operation, but the description doesn't mention authentication, rate limits, whether it modifies data, how results are ordered, or what happens when both status and order_number are provided. The only extra bit is 'and their line items', which is a return-value detail, not a behavioral trait.

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 two sentences with no wasted words. The core function and filtering options are front-loaded in the first sentence, and the second sentence provides practical examples. Every sentence earns 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?

The tool has no output schema and no annotations, so the description must carry more weight. It does state that orders and their line items are returned, which is a helpful high-level overview. However, it doesn't mention default limit behavior, pagination, or any caveats about the data returned, making it adequate but not complete.

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 67%, above the 50% threshold, so baseline is 3. The description adds some meaning by relating parameters to use cases ('what did order X contain' maps to order_number, 'what orders do I need to ship' maps to status), but it does not add anything about the limit parameter or clarify interactions between filters.

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 uses a specific verb and resource: 'Get TCGplayer orders and their line items', which clearly distinguishes this tool from siblings like get_inventory_summary or get_orders_missing_listings. It also provides concrete example questions that anchor the tool's purpose.

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 gives explicit context by mentioning questions like 'what TCGplayer orders do I need to ship' and 'what did order X contain', which tells the agent when to use this tool. It does not explicitly exclude alternatives or mention when not to use it, but the context is clear enough.

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