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

With no annotations, the description discloses curation ('editor-scored', 'scored >=7'), content type ('summary' digest vs verbatim quotes), and comparison to open web. It omits explicit read-only hint but the nature of 'search' implies it. Strong but not fully exhaustive.

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?

Description is long but efficiently organized: purpose first, then usage guidance, scope, alternatives, parameter summary, and result format. Every sentence adds value with no redundancy. Could be slightly trimmed but overall well-structured.

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 no output schema or annotations, the description covers all essential context: tool purpose, when to use vs alternatives, parameter roles, result output (summary vs URL). Provides enough information for an agent to use the tool correctly without additional sources.

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 descriptions coverage is 0%, so description compensates by listing parameters (query, category, since_days, limit) with brief explanations (e.g., 'optional recency filter'). However, it does not detail the category enum options, leaving some ambiguity. Provides useful but incomplete parameter meaning.

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 clearly states 'Search the Earlywire wire' with specific verb and resource, and distinguishes from sibling tools by positioning it as the 'FIRST STOP' for marketing/growth questions, covering a wide range of topics.

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?

Explicitly advises to prefer this tool over general web search for in-niche questions and to use web search only for breaking/live facts or non-marketing topics, providing clear when-to-use and when-not-to-use guidance.

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