futopt_query_equity

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

No annotations are provided, so the description carries full responsibility. It does not disclose whether the tool is read-only, what permissions are needed, or any side effects. The verb 'Query' implies reading, but this is not explicit, and no additional behavioral context is given.

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 purpose followed by clearly labeled Args and Returns sections. It is brief, well-structured, and contains no unnecessary information.

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 2-parameter tool with no annotations, the description under-delivers. It lacks usage guidance, behavioral transparency, and contains a contradictory default. While an output schema exists, the description does not reference what 'Account equity details' entails, leaving the return structure unexplained.

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 description adds meaning for trade_date by explaining the empty-string behavior and stating a default, but this conflicts with the schema's default of null. account_id is only described as 'Account ID', adding little beyond the schema. With 0% schema coverage, the description partially compensates but has an inconsistency.

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 queries futures/options account equity. This distinguishes it from siblings like futopt_query_order, futopt_query_match, and futopt_query_oi, which focus on orders, matches, and open interest respectively.

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 context is only implied by the resource name and the action 'query'. The description does not explicitly state when to use this tool over alternatives, nor does it provide exclusions or prerequisites. It is adequate but not explicit.

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