explain_mechanic

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

Discloses offline/deterministic nature and attribution requirements. No annotations provided. Lacks details on error handling or performance, but sufficient for a read-only knowledge 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?

Well-structured and concise. Front-loaded purpose, followed by return details, examples, and fallback instructions. No redundant sentences.

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 single param and output schema, description covers key aspects: data source, attribution, curated topics, and fallback. Complete enough for agent to understand usage.

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 0% schema description coverage. Description adds example topic values (resistances, ailments, etc.) but does not explain format or constraints. Partially compensates 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?

Clearly states the tool explains a Path of Exile 2 mechanic using offline deterministic corpus. Specifies return value (principle + wiki page) and lists example topics. Distinguishes from siblings like search_mechanics and lookup_mechanic.

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 provides when-not-to-use and alternatives: 'If nothing matches, use search_mechanics to browse, or lookup_mechanic to fetch a page live from the wiki.'

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