create_locate

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

No annotations are provided, so the description carries the burden. It transparently indicates this is a mutation (creates) and specifies required inputs, but it does not disclose what happens upon success, whether the locate is a hard check, or any permission requirements. The schema adds some behavioral detail (e.g., HTTP 400 for invalid quantities), but the description itself is thin beyond the basic action.

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 that front-loads the action and purpose. Every word contributes value, with no filler or redundancy.

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?

The tool has 4 parameters and an output schema, and the description plus detailed schema provide enough context for an agent to select and invoke the tool correctly. It could mention preconditions or the locate life cycle, but the combination of description and schema covers the essential information.

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 description coverage is 100%, so the baseline is 3. The description restates which parameters are required and optional but adds no new semantic information beyond the schema's already-detailed descriptions (e.g., round lots, decimal string for limit_price).

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 uses a specific verb 'Creates' with a clear resource ('locate request for a short sale'), and explicitly lists required versus optional parameters. It clearly distinguishes itself from sibling tools like get_locates and get_locate, which query existing locates.

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?

The description clearly states this tool is for creating a locate request and identifies the minimum required inputs (symbol and quantity). It does not explicitly direct users to alternatives (e.g., get_locates for checking existing requests), but the creation context is unambiguous enough for an agent to infer when it should be used.

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