Get competitive intelligence

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

Annotations already provide readOnlyHint and openWorldHint. The description adds valuable context: the `{data:null}` response for unsupported tickers should be treated as 'no data' not an error, and clarifies the output is qualitative. This goes beyond the annotations.

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?

Two sentences, front-loaded with the core purpose and output content, followed by a concise caveat. No wordy or redundant information.

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 simple one-parameter, read-only tool, the description covers the output contents and the key edge case (null data for certain tickers). It stops short of describing the exact return structure, but given the low complexity, this is sufficiently complete.

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 input schema only defines a required string 'ticker' with 0% description coverage. The description says the tool is 'for a ticker' and implies the ticker should be a mid/small-cap, but it does not define the ticker format or any constraints beyond that, only partially compensating for the missing schema description.

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 identifies the tool's purpose: 'Qualitative competitive intelligence for a ticker' and specifies the exact content areas (economic moats, structural weaknesses, upcoming catalysts, peer comparison). This distinguishes it from sibling tools like catalyst-specific or evidence-focused tools.

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?

Explicitly states when to use ('Best for mid/small-caps') and when the tool is less appropriate (mega-caps and thinly-covered names may return null data). However, it does not name an alternative tool, so it lacks the full 'alternatives' guidance.

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