get_marketplace_order

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

With no annotations the description must disclose behavior. It fails to mention that this is a read-only operation or any side effects, rate limits, or required permissions. The description provides no behavioral insight.

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, it is under-specified rather than concise. It wastes the opportunity to provide necessary details, so it scores low.

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 incomplete parameter documentation, the description is wholly inadequate. It does not explain what the tool returns or how to use it effectively.

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 schema has a single parameter 'order_id' with no description and 0% schema coverage. The description does not explain what 'order_id' is or how to obtain it, leaving the agent guessing.

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 'Get a marketplace order' states the verb and resource but lacks scope or differentiation from siblings like 'get_marketplace_orders' and 'get_marketplace_order_messages'. It is vague but not a pure tautology.

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 provided on when to use this tool versus alternative tools such as 'get_marketplace_orders' for listing orders or 'get_marketplace_order_messages' for messages. The description offers no context for usage.

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