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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations by explaining the exact-text matching rule and its consequences: it catches copypasta but misses reworded campaigns. This meaningfully informs expectations about result precision.

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 with no wasted words. The core function appears first, and the critical matching limitation follows immediately. Every phrase earns 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?

For a zero-parameter read-only tool, the description is largely sufficient: it states what is detected and how matching works. Because no output schema is provided, a little more detail about the return structure or field contents would make it fully complete, but the current description already covers selection and invocation needs.

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 has zero parameters Registry coverage is 100% by default, and there are no parameters for the description to document. Per the zero-parameter baseline, the description is not expected to add parameter semantics, so a score of 4 is appropriate.

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 subject as 'coordinated posting campaigns' and specifies the exact-text matching mechanism, which makes the function concrete. It stops short of an explicit verb like 'Returns' or 'Fetches', and it does not name sibling tools, so differentiation relies on the semantic content rather than a direct comparison.

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 this tool should be used instead of related tools such as get_signal_integrity, get_social_posts, or get_similar_posts. The exact-text caveat implies a limitation, but it does not explicitly state the conditions under which an agent should choose this tool over an alternative.

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