Drift Open Perp Position

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

Annotations already indicate it is a write operation (readOnlyHint=false) and not destructive. The description adds no behavioral context beyond this, such as expected responses, failure modes, or permission requirements. With annotations present, the description fails to add value.

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 not concise. After a one-line purpose, it devotes a full paragraph to SAP context that is not essential for using this tool. Every sentence should be justified; the SAP note is better placed elsewhere.

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 tool has 9 parameters, 4 required, and involves opening a perpetual position, the description lacks information about outcomes, position management, or how the returned data (output schema exists) should be interpreted. The SAP context is irrelevant for completeness.

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 100% description coverage for all 9 parameters, so the schema already documents parameters adequately. The description does not add or clarify any parameter behavior beyond what is in the schema, so a baseline score of 3 is appropriate.

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 first sentence clearly states the tool opens a perpetual futures position on Drift, which is a specific verb and resource. It distinguishes from sibling drift tools like close and get positions. However, the inclusion of a long paragraph about SAP context dilutes the focus slightly.

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 is given on when to use this tool versus alternatives such as adrena_openPosition or other perpetual trading tools. The only usage advice refers to SAP registration tools, which is unrelated to the core function.

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