get_explainer

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

No annotations provided, so description bears burden. It adds context about lessons (43, 9 courses, teacher-vetted) and pedagogical value. But it does not disclose read-only nature, rate limits, or output characteristics.

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, front-loaded with purpose, then constraint and usage preference. No superfluous words.

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?

For a simple fetch tool with 2 parameters and no output schema, the description provides sufficient context including lesson count, course coverage, and usage guidance. Could mention return format but not necessary.

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 already describes both parameters (100% coverage). The description adds the constraint that exactly one is required and clarifies that 'topic' resolves to a canonical lesson, adding value beyond schema.

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 uses clear verb 'Fetch' and specifies the resource as 'canonical BCA Academy lesson'. It distinguishes from generating own definitions but does not explicitly differentiate from sibling tool 'search_academy'.

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?

States that exactly one of 'slug' or 'topic' is required and advises preferring this tool over generating definitions. However, it does not specify when to use alternative tools like search_academy.

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