qualify_contracts

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

No annotations are provided, and the description only hints that the tool modifies data ('fill in missing fields'), but it does not disclose whether it is destructive, rate limits, authentication needs, or other behavioral traits. The agent lacks awareness of side effects.

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, which is concise, but it lacks structure. It does not front-load the key purpose or parameters. It earns its place but at the expense of completeness.

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?

With no output schema, no annotations, and 4 parameters at 0% coverage, the description is severely incomplete. It does not explain return values, behavior, prerequisites, or how the tool handles errors. The agent cannot reliably invoke this 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 description coverage is 0%, so the description should compensate, but it only mentions conId as an example missing field. The four parameters (contract_type, symbol, exchange, currency) are not elaborated upon, leaving the agent unsure about valid values or formats.

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 'Qualify contracts to fill in missing fields like conId,' which gives a general idea of completing contract data, but the verb 'qualify' is ambiguous and not a standard action. It distinguishes from siblings like create_contract and get_contract_details but lacks precision.

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 provides no guidance on when to use this tool versus alternatives like create_contract or get_contract_details. There are no exclusions or context for when this tool is appropriate.

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