find_risk_precedents

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

No annotations provided. Description mentions lookback_days is not used, which is a behavioral trait, but fails to disclose return structure, side effects, or permissions. Output schema exists but unmentioned.

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?

Short and front-loaded sentence. Could benefit from clearer bullet formatting, but no unnecessary content.

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 output schema present and 2 parameters, description is sparse. Lacks details on return value, risk interpretation meaning, or example use case.

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%. Description adds examples for signal_types and notes lookback_days is unused, partially compensating. However, lacks full semantics like valid formats or constraints.

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 returns characteristics and risk interpretation of signals based on signal types. The verb 'returns' is specific, but 'find_risk_precedents' implies precedents, while description focuses on interpretation. Slightly misaligned but still clear.

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 versus siblings like 'analyze_company_risk' or 'check_disclosure_risk'. Description does not provide context or exclusions.

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