ihyee-mcp

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: uses Google search, fetches and extracts content (clean text, summaries, links), and mentions browser rendering as an option. However, it lacks details on rate limits, authentication needs, error handling, or what 'extracted' entails beyond summaries and text.

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 appropriately sized with two sentences that efficiently convey the core functionality. It's front-loaded with the main purpose and adds implementation details without redundancy, though it could be slightly more structured for clarity.

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 the complexity (7 parameters, no output schema, no annotations), the description is moderately complete. It covers the tool's purpose and high-level behavior but lacks details on output format, error cases, or integration with siblings. Without an output schema, it should ideally hint at return values like structured data with links and summaries.

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 schema fully documents all 7 parameters. The description adds no parameter-specific semantics beyond implying the tool handles search queries and content extraction, which is already covered by the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 states the tool's purpose with specific verbs ('search the web', 'return extracted, summarized content') and resources ('top results', 'Google search', 'result pages'). It distinguishes from siblings by specifying it's a search tool that extracts content, unlike ihyee_fetch or ihyee_render which likely have different functions.

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 description provides no guidance on when to use this tool versus its siblings (ihyee_fetch, ihyee_render). It mentions the general function but doesn't specify scenarios, prerequisites, or exclusions that would help an agent choose between alternatives.

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