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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), and the description usefully adds the API-key requirement, which is auth context not in the structured fields. It does not explain what the non-read-only behavior actually does or what state is affected, leaving a gap for a tool whose 'get_' name sits awkwardly against readOnlyHint=false.

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 short sentences with no padding, and the primary function is front-loaded ahead of the prerequisite. It is not a 5 only because the lead sentence describes an outcome rather than the tool's action, so the front-loading spends its first words on the wrong thing.

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?

An output schema exists, so return values need not be described, and the auth prerequisite is disclosed. However, for a tool with a mismatched name/description and twelve siblings, the description leaves the core question — what it retrieves and when to prefer it — under-specified.

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?

There is a single parameter with 100% schema description coverage ('URL to analyze'), so the schema already carries semantics and the baseline is 3. The description adds nothing about the URL (e.g., is it a page, a property, a competitor site?) beyond what the schema states.

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 name and title say 'Get Opportunities', but the description instead talks about 'prioritizing audit issues' — a related but not identical effect, so the tool's actual action (retrieve opportunity data for a URL) is never plainly stated. It does imply analysis over a target, but does nothing to distinguish it from siblings like seo_audit or generate_fixes.

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 only guidance is the prerequisite 'Requires API key'. There is no statement of when to call this versus the many comparable siblings (seo_audit, generate_fixes, get_site_info) and no exclusions or context triggers.

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