Collimer AI-visibility scan

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

Annotations declare readOnlyHint and openWorldHint. Description adds that the scan is free, returns specific data, and that full report requires a free account. No contradictions with annotations.

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?

Four sentences, all informative. Front-loaded with main purpose. No fluff or redundant text.

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?

No output schema, but description details what is returned (score, confidence interval, gap, report URL) and explains the limitation of the free scan. Adequate for a 2-parameter tool.

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 100%. Description adds value by explaining 'email' is optional and speeds account claiming, and gives example formats for 'domain' (e.g., 'example.com' or 'https://example.com').

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?

Description states it runs a free Collimer scan to measure AI-visibility, specifies the engines (ChatGPT, Claude, Gemini, Perplexity, Google AI Overviews), and lists returned items (score, confidence interval, gap, report URL). Clearly distinguishes from sibling 'collimer_scan' as a deprecated alias.

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?

Provides context on when to use (measuring brand visibility) and a tip to re-run after changes. Mentions deprecated alias to differentiate from sibling. Does not explicitly state when not to use or provide alternative tools.

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