lookup_mechanic

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

Discloses live network call, returns short extract + source link, may be outdated, returns {available: false} if unreachable, single user-triggered, read-only, never sends build data. No annotations provided, so description carries full burden and covers well.

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?

Fairly concise with line breaks. Every sentence adds value, but slightly redundant (e.g., 'live' mentioned twice). Could be tighter.

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 output schema exists, description doesn't need to detail returns, but it mentions extract + source link and error case. Single parameter, good coverage of context. Complete.

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?

Only one parameter 'topic' with no schema description (0% coverage). Description explains its purpose ('mechanic/skill/item explanation') but lacks examples or format constraints. Baseline 3 with some compensation for low coverage.

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 fetches a mechanic/skill/item explanation from the PoE2 Wiki live. It distinguishes itself from siblings explain_mechanic and search_mechanics by noting it's a live network call.

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 says 'use this only when explain_mechanic/search_mechanics don't have the topic in the bundled corpus,' providing clear when-to-use guidance and naming alternatives.

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