get_offer

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It mentions the response includes trade stats and time remaining, which is helpful, but it does not explicitly state the operation is read-only or cover error handling/auth requirements. The verb 'Get' implies safety, but the description adds limited behavioral context beyond that.

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 of ten words, front-loaded with 'Get full details of a single offer' followed by clarifying content. Every word earns its place, with no redundancy or filler.

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 (one parameter, no output schema, no annotations), the description provides a clear sense of the returned data (trade stats, time remaining) and the scope (single offer). It omits details about error behavior and authentication, but these gaps are partially mitigated by the simplicity of the operation and the schema's parameter description.

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 already provides full coverage for the sole parameter 'offerId' with a clear description ('Offer UUID'), so the baseline is 3. The tool description does not add any extra meaning or context to the parameter, so it neither enhances nor detracts from the schema.

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 the specific verb 'Get' with the resource 'full details of a single offer', clearly distinguishing it from sibling tools like list_offers that return collections. It also specifies content such as 'trade stats and time remaining', making the tool's purpose unmistakable.

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 implies usage for fetching one offer by ID, but it does not explicitly state when to use this tool instead of alternatives like list_offers or get_my_offers. No exclusions or alternative tool references are provided, so usage guidance relies on inference.

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