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

Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior, and the description adds valuable context beyond them: the tool makes external calls to third-party LLMs (an important side-effect/cost signal) and explicitly disclaims answering questions or delegating work. It falls short of 5 only because it doesn't disclose rate-limit or cost implications of firing queries at four external providers.

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 front-loaded with the core purpose in the first sentence, then the competitive-audit framing, then a tightly organized routing block. Every sentence earns its place — there is no filler, and the negative routing content is high-value despite its length.

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 5-parameter tool with external side effects and no output schema, the description covers purpose, scope, routing exclusions, and alternatives thoroughly. It is missing only a note on what the result looks like (e.g., per-provider mention report) and cost/rate-limit transparency, which would make it fully complete.

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%, so the baseline of 3 applies; the schema already richly documents providers (mapping enum values to brand names and noting Perplexity's Sonar Pro live-search advantage) and prompt semantics. The tool description adds no additional parameter-level meaning beyond what the schema provides, but no compensation is needed given full coverage.

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 names a specific verb and resource ('Audit whether FreedomOS appears in AI-generated search results') and explains the concrete mechanism (sending queries to Claude, Grok, Gemini, Perplexity and checking for brand mentions). It also distinguishes itself from siblings by explicitly stating it is not a general research or Q&A tool, which separates it from browse_url, read_web_page, and query_sme in the sibling list.

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 Routing paragraph is exemplary: it gives positive routing (SEO/GEO visibility, competitor, and content-strategy research with concrete example queries) and explicit negative routing (NOT for a second opinion, NOT to answer user questions, NOT general research) while naming the exact alternatives (browse_url/read_web_page). An agent can route this tool correctly without any inference.

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