Fulfillment Orders Get

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

The description provides critical behavioral metadata that is outside of the structured annotations, namely the specific HTTP method (GET), the full API endpoint path, and the required security scope. This is essential for correct invocation and authorization.

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 highly dense and concise, front-loading the core function and immediately following with the technical implementation details (HTTP method and URL path).

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?

By providing the full URL structure, required scope, and identifying the exact version, the description provides maximum technical context necessary for an agent to successfully attempt the API call.

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?

While the input schema covers 100% of parameters, the description adds valuable context by including the API version (2025-03) and confirming the usage context (e.g., that it retrieves a specific instance), elevating it above a baseline score.

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 the function ('Get one fulfillment order') and distinguishes this specific resource retrieval from generic order or list-based siblings by naming the resource path components.

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 is clear that the function retrieves a single record based on the provided context (order_id and id). While it does not explicitly name all alternatives, the specific resource retrieval implies it is not a list operation.

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