Search curated EQL sources

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description only says 'Search across curated... pages' with no mention of authentication, rate limits, result format, or side effects. This is insufficient for a search tool.

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?

Two concise sentences with no wasted words. The action is front-loaded ('Search across...'), and the guidance is direct. Every sentence adds value.

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 three parameters, no output schema, and no annotations, the description is too brief. It does not clarify the scope of 'curated', how results are presented, or pagination behavior. A search tool needs more context for effective use.

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 67% (descriptions for 'query' and 'sourceIds' but not 'limit'). The description does not add any extra meaning or usage context beyond the schema. It fails to explain important parameters like 'limit' or 'sourceIds', leaving the agent to rely solely on the schema.

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 searches across curated official, support, and guide pages. It also distinguishes from sibling tools by advising to use wiki-specific tools for full wiki search. The verb 'search' and resource 'curated sources' are specific.

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 clear context: it is for searching curated pages, and explicitly says to use wiki-specific tools for full wiki search. This gives a when-not-to-use hint. However, it does not detail alternatives among the many sibling tools or specify prerequisites.

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