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

Annotations are empty, placing full burden on the description. It does not disclose behavioral traits (e.g., read-only, side effects, data aggregation method). 'Signal intel only' is too vague to assess impact or safety.

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 very concise at two sentences, efficiently conveying core purpose. It could be slightly more structured (e.g., separating usage notes), but it avoids verbosity.

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 2 parameters and no output schema or annotations. The description fails to explain what a 'cluster brief' contains, output format, or how to interpret results, leaving gaps for effective use.

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 must explain parameters. It does not mention 'limit' or 'ticker' at all, leaving their semantics entirely to the schema, which only provides ranges without context.

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 clearly states the tool's purpose: transforming recent SEC Form 4 filings into an 'insider-activity cluster brief.' The phrase 'Signal intel only' distinguishes it from more detailed sibling tools like 'insider_trades' or 'edgar_filings.'

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 hints at usage with 'Signal intel only,' suggesting it's for quick signals rather than deep analysis. However, it does not explicitly state when to use this tool vs. alternatives or provide when-not contexts.

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