investor_research_instrument

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

No annotations provided, so description carries the burden. It only mentions external sources not wired, which is vague. Does not disclose behavior for invalid input, side effects, or data freshness. Insufficient for a research generation tool.

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?

Very concise at two sentences, no fluff. However, the second line appears as a quote and could be integrated more clearly. Lacks structured formatting but efficient.

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?

Missing details on return values (no output schema), error handling, prerequisites, and overall workflow. For a 3-parameter tool with no annotations, the description is too sparse to be fully actionable.

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 0%, but description adds meaning for 'instrument' (structure) and 'depth' (options). The 'focus' parameter is not explained. Partially compensates for missing schema descriptions.

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?

Description clearly states it prepares a research draft for an instrument/issuer. The verb 'Prepare' distinguishes it from retrieval tools like investor_get_instrument, but could be more specific about the action (e.g., creating a draft).

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?

No guidance on when to use this tool vs alternatives. The note 'external sources not wired yet' hints at limitations but does not clarify proper context or when not to use it. No siblings mentioned.

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