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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful context beyond annotations: the data source (SEC EDGAR), the focus on fundamental ratios, latest filing context, and a deterministic signal. It does not detail response shape or rate limits, but it does not contradict annotations and adds useful behavioral color.

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, information-dense sentence with no filler. The main action and resource appear first, followed by a compact list of output categories. Every clause contributes to understanding the tool's purpose and scope.

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?

For a tool with one required parameter and no output schema, the description names the input and the main output categories, which is largely sufficient. It could be more complete by explaining what the 'deterministic fundamental signal' means or by directing users to sibling tools for other intelligence types, but nothing essential to invoking the tool is missing.

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?

The only parameter, symbol, is already fully described in the input schema with ticker examples. The description reinforces that it is a US equity but adds no new parameter-level semantics such as format constraints, accepted exchanges, or edge cases. Baseline 3 is appropriate given 100% schema description coverage.

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 a specific verb ('Get'), a precise resource ('SEC EDGAR-derived fundamental intelligence'), and a clear scope ('for a US equity'). It enumerates the content areas (growth, margins, balance-sheet ratios, filing context, fundamental signal), which helps distinguish it from broader sibling tools like get_symbol_intelligence or get_market_intelligence.

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 implies when to use this tool: when a caller needs SEC filing-based fundamental metrics for a single US equity. However, it does not explicitly name alternative siblings or state when not to use this tool, so exclusions and routing guidance are absent.

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