wikipedia

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

Discloses basic behavior (summary vs full text via sentences parameter and language support), but with no annotations, the description does not cover error handling, rate limits, or what happens if articles are missing. Adequate but not thorough.

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?

Well-structured with clear purpose, detail, and sample prompts. Sample prompts add length but provide useful context. Minimal fluff.

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?

Explains inputs and output sufficiently for a simple lookup tool. Missing error handling or alternative tool guidance, but output schema exists. Adequately complete for typical 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?

Adds significant meaning beyond schema titles: defines query as topic, language with examples and default, sentences with interpretation of 0. With schema descriptions absent, this fully explains parameter semantics.

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 'Look up a Wikipedia article and return its content,' specifying verb and resource. Identifies return type (summary or full text) and language support, distinguishing it from sibling search tools like google_search which return search results.

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?

Implied usage via sample prompts, but lacks explicit guidance on when to prefer this tool over alternatives or when not to use it. No mention of exclusionary conditions or alternatives.

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