Read EQL Wiki page

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

No annotations provided, so description carries full burden. Discloses core behavior (fetch, return components, era advisory) but omits error handling, authentication needs, or rate limits. Reasonably transparent for a read-only fetch.

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 sentences: first covers core action and outputs, second adds a key behavioral note on eraAdvisory. No extraneous words, front-loaded with essential information.

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?

Adequate given simple tool with 2 params and no output schema. Covers basic functionality and a special case, but lacks details on return format (e.g., JSON structure), error scenarios (e.g., page not found), and how to interpret outputs like links and categories.

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 covers both parameters fully. Description adds value by specifying the return structure (extracted text, links, categories, revision metadata) beyond the schema. This compensates for the schema's focus on input alone.

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?

Clearly states the verb 'fetch', resource 'page from EQL Wiki', and specific outputs (extracted text, links, categories, revision metadata). Includes unique detail about eraAdvisory, distinguishing it from sibling tools like search or category listing.

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?

Implies usage when needing a specific page's content, but lacks explicit guidance on when to use this tool versus alternatives like eql_wiki_search or eql_wiki_category_pages. No when-not-to-use instructions.

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