explain_concept

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

No annotations provided, so description carries full burden. It discloses that the explanation is tailored, returns examples and links, and uses Kadmia progress. No mention of side effects, permissions, or state changes, but for a read-only explanation tool this is adequate.

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, no redundancy. Front-loaded with purpose, directly followed by outcome.

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?

No output schema, but description explains return (explanation with examples and links). Sufficient for a simple tool, though could detail how depth and context parameters influence output.

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 all parameters 100%. Description adds value by explaining personalization based on skill level (not in schema) and hinting at context usage. Depth enum is clear in schema, so no extra needed.

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's purpose: to explain a concept tailored to the user's skill level and progress in Kadmia, with examples and links. It distinguishes from siblings (bookmark, challenge, progress check).

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 implies when to use (when needing an explanation), but lacks explicit guidance on when not to use or alternatives. It does not mention that it is for learning contexts or that it personalizes based on progress, leaving some ambiguity.

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