get_order

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

Since no annotations are provided, the description carries the burden of communicating behavioral traits. 'Get' clearly indicates a read operation and 'authenticated' signals that authorization is required. The description does not disclose not-found behavior, response structure, or rate-limit considerations, but for a simple single-resource fetch this is minimally adequate.

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 with no unnecessary words, and the core action and resource are front-loaded. Every word contributes to meaning. It is concise without being under-specified.

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 low complexity of the tool—one required parameter and no output schema—the description covers the basic purpose and authentication context. However, it omits information about the returned order details, error behavior, and how this tool relates to sibling order tools. It is minimally complete for a straightforward fetch.

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 parameter descriptions and 0% schema coverage, so the description must compensate. It adds useful context by indicating that orderId refers to a marketplace order rather than a generic order, helping to disambiguate from other tools. However, it does not explain the ID format or how an agent should obtain the orderId, so the compensation is only partial.

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 states a specific verb ('Get') and resource ('authenticated marketplace order'), making it easy to identify this as a single-order fetch. The singular phrasing and required orderId distinguish it from list-oriented siblings like get_orders and mutation tools like edit_order. It does not simply restate the tool name or use vague wording.

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 provides no explicit guidance on when to use this tool versus its siblings such as get_orders, edit_order, or get_order_messages. The word 'authenticated' hints that the order belongs to the authenticated user, but no conditions, prerequisites, or alternatives are mentioned. An agent must infer the appropriate use from the name and parameter schema.

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