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

Annotations already establish readOnly/idempotent/openWorld/non-destructive behavior, and the description adds meaningful context beyond that: keyless public endpoint is 'heavily rate-limited', results are 'CC-BY-NC-SA 4.0 licensed' with a commercial-key requirement, and the response returns 'url, title, description, a quality score, and how many other results share the domain'. No contradiction 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?

The description is long but dense and wasteful only in the sense that every sentence carries a distinct fact: what it is, when to use it, what it returns, its weaknesses, and licensing. The core purpose and routing guidance are front-loaded before the return-format and licensing details.

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?

There is no output schema, yet the description pre-announces the return fields (url, title, description, quality score, domain count), the licensing behavior, and the rate-limit caveat. For a tool with one required parameter, an agent has everything needed to call it and interpret results correctly.

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 coverage is 100% with descriptive parameter docs, including defaults, ranges, and tips like 'Use a low value like 2 to force variety across sites' for max_per_domain. The description adds no parameter-level semantics beyond what the schema already provides, so the baseline of 3 applies.

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 opens with a specific verb+resource pair, 'Search the INDEPENDENT Marginalia web index', and immediately distinguishes it from mainstream search tools by noting it is 'NOT Google/Bing-derived (unlike serper_search / exa_search / serpapi)'. This lets an agent tell it apart from sibling search tools without opening any schema.

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?

It gives explicit when-to-use guidance: 'Use it when mainstream search results are dominated by SEO content, listicles, and marketing pages, or when you want a second opinion'. It also states exclusions and routes the agent to an alternative: 'Weak for breaking news, e-commerce, and mainstream/celebrity topics — use serper_search for those.'

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