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

No annotations are provided, and the description offers zero behavioral insight. It does not disclose read-only vs. mutating behavior, pagination, response format, rate limits, or any side effects. The description adds no value beyond the structured fields.

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?

While the description is short, this is under-specification rather than conciseness. The single sentence is a tautology that wastes the agent's attention without providing any substantive content. There is no structure or front-loading of useful 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?

This is a complex 15-parameter tool with no output schema and no annotations. The description should explain the purpose, filtering capabilities, and return value structure, but it fails to address any of these. It is completely inadequate for safe and effective invocation.

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?

With 15 parameters and 0% schema description coverage, the description was expected to compensate by explaining parameter meanings and relationships. Instead, it says nothing about any parameter, leaving the agent to guess the purpose of fields like 'promptId', 'withCompetitors', or 'sentiment'.

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 'Get content opportunities.' is a verbatim restatement of the tool name and title. It does not explain what constitutes a content opportunity, what the tool returns, or how it differs from sibling tools like get_backlink_opportunities or get_community_opportunities.

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 gives no guidance on when to use this tool versus alternatives. It mentions no prerequisites, use cases, or exclusion conditions, leaving the agent without situational context.

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