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

No annotations are provided, so the description must carry the full burden. It mentions the source registry and that it's 'what the agent/bots have open', but it does not explicitly state that this is a read-only operation, nor does it disclose any side effects or behavioral traits. The name 'get' implies read-only, but the description doesn't confirm safety.

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?

Extremely concise, single sentence plus a param listing. Front-loaded with the core purpose and no filler. Every word earns its place.

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 read tool with two optional parameters and no output schema, the description gives the source and scope but lacks details on return structure, pagination, or any filtering nuances. It's minimally complete but doesn't fully guide the agent on expected output.

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?

Schema coverage is 0%, so the description must explain the parameters. It lists exchange and symbol and marks them as optional, but provides no details on valid values, formats, or how they filter the results. It adds minimal value over the schema, which already lists types.

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 (user's open positions from the registry), and adds clarification about agent/bot ownership. However, it does not explicitly differentiate from sibling position tools like list_hedge_positions or get_portfolio, so it's slightly less than excellent.

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 on when to use this tool versus alternatives. It doesn't mention when not to use it, nor does it reference any sibling tools for comparison. The agent must infer usage from the name and context.

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