offsets__get_purchase

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

With no annotations provided, the description carries full burden. It only states 'Fetch', implying read-only, but does not disclose any potential side effects, authentication needs, error handling, or behavior for invalid IDs.

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 very short and front-loaded with domain context in brackets. Every part serves a purpose, though a slight expansion on parameter format would not hurt.

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?

For a simple fetch-by-ID tool with one parameter and no output schema, the description provides the essential functionality. However, it lacks details on return format, errors, and within-domain context that would fully equip an agent.

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 0% coverage, and the description only mentions 'by id' without explaining the purchase_id parameter's format, constraints, or examples. It adds minimal value beyond identifying the parameter's purpose.

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 tool fetches a past purchase/offset certificate by ID, using the verb 'Fetch' and specifying the resource. It distinguishes from sibling tools like offsets__buy_offset or offsets__book by focusing on retrieval of existing records.

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 explicit guidance on when to use this tool versus alternatives, such as offsets__list_credit or offsets__net_position. The use case is implied by the description but lacks clear direction on prerequisites or scenarios to avoid.

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