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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only implies a read operation via 'Get' but reveals nothing about pagination, required parameters, filtering semantics, output structure, or side effects. With zero behavioral detail, the agent cannot anticipate the tool's actions or requirements.

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 short sentence, but this is under-specification rather than genuine conciseness. It does not front-load useful information; it simply repeats the tool name. Every word fails to earn its place.

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?

Given the tool's complexity (15 parameters, 4 required, no output schema, no annotations), the description is grossly inadequate. It fails to explain what 'community opportunities' are, how to use the parameters, or what output to expect, leaving the agent with insufficient context for correct 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?

Schema description coverage is 0%, and the description mentions none of the 15 parameters (e.g., page, pageSize, startAt, endAt, platforms, sentiment). The description adds no meaning to the bare schema, which itself lacks parameter descriptions, leaving all parameter semantics unexplained.

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 community opportunities.' is a direct restatement of the tool name and title, providing no additional specificity. It does not distinguish this tool from siblings like 'get_content_opportunities' or 'get_backlink_opportunities', and the phrase 'community opportunities' remains undefined.

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?

There is no guidance on when to use this tool versus alternatives. No context, prerequisites, or exclusions are mentioned, leaving the agent entirely without direction for tool selection.

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