Estimate Max Purchase Quantity

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

Annotations already declare readOnlyHint, destructiveHint=false, idempotentHint=true, so description adds limited behavioral insight beyond that. Mentions return format (decimal strings) and case-insensitivity, but no additional side effects or limitations.

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: first states purpose and return format, second covers parameter guidance. No unnecessary words; all information is front-loaded and relevant.

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?

Covers purpose, parameters, and return format briefly. With output schema available (but not shown), the description's output indication is sufficient. Could mention that order_type and price affect the estimate, but overall complete for a simple estimation tool.

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 100%, but description adds value by stating defaults (side defaults to Buy, order_type to LO), case-insensitivity, and optional nature of price. This clarifies usage beyond schema, which only lists defaults without case-insensitivity.

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?

Clearly states the verb 'Estimate' and resource 'maximum buy/sell quantity for a symbol'. Distinguishes itself from sibling order-related tools (e.g., submit_order) by focusing on estimation of max quantity, not execution.

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?

Provides basic parameter guidance (only symbol required, defaults, case-insensitivity) but lacks explicit when-to-use vs. alternatives (e.g., when planning an order vs. submitting one). Implied context but no exclusions.

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