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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds real value beyond that with the prompt-injection warning about {"untrusted_text": ...} fields, a behavioral trait annotations cannot express. It stops short of pagination, error, or empty-result behavior.

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?

Two sentences, front-loaded with the scope and field list, with the security caveat correctly placed last. The dense field enumeration is justified since no output schema exists, though it reads as a run-on.

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?

There is no output schema, so the description usefully compensates by enumerating return fields and flagging the untrusted-text hazard. Missing only secondary details such as ordering, empty results, and multi-account behavior.

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?

With a single parameter at 100% schema coverage, the schema already documents account_id fully (including the list_accounts pointer). The description adds no input-parameter detail; its 'id (use it as order_id)' note concerns a returned field, not an argument. Baseline 3 applies.

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 states a specific resource (pending, not-yet-filled orders) and enumerates the returned fields, which distinguishes it from get_history and get_positions. It never names a sibling explicitly, but the 'pending' scope is enough for an agent to route correctly.

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?

Usage is only implied: an agent can infer it should call this to inspect open orders, but there is no explicit when-to-use, when-not, or reference to alternatives like get_history or get_positions. The 'pending (not yet filled)' qualifier is the only scoping signal.

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