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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that: it lists the exact data categories returned (performance, SEO, Core Web Vitals, authority, G2/Product Hunt presence, content freshness, and founder edits) and notes it is 'free.' It does not discuss pagination or rate limits, but with annotations carrying the safety burden this is adequate.

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 front-loaded with the resource and its contents, then moves to usage guidance and finally a brief safety/cost note. The first sentence is dense with parenthetical detail but remains readable; overall it is appropriately sized with little waste.

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 no output schema, the description carries the burden of explaining return values, and it does so by enumerating the stat battery and founder edits. It also covers when to read the tool and its read-only/free nature. Completeness is strong, though it could mention pagination or sibling alternatives for an even fuller picture.

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 tool takes no parameters, so there is no parameter semantics to document. The baseline for zero parameters is 4, and the description does not need to compensate for any input schema gaps.

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 names a specific resource (competitor roster) and enumerates the measured stat battery and founder edits it returns, which clearly distinguishes it from siblings like get_seo or get_visibility. It lacks an explicit verb such as 'returns' or 'lists', but the content is specific enough for an agent to know exactly what this tool provides.

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?

It explicitly states when to read it: 'before any competitor or outreach work so a rival is never treated as a pitch target.' This is clear contextual guidance, though it does not name alternatives or state when not to use it.

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