academy_playbook

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

The readOnlyHint annotation already signals a read operation, and the description adds the 'full text' detail, which clarifies the return nature. However, it provides no context on response format, potential errors, or any special behaviors beyond that.

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?

The description is a single, efficient sentence with zero filler. It immediately fronts the key verb and object, making it easy to parse.

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 retrieval tool with two parameters and no output schema, the description is adequately complete. The annotation and sibling context fill in remaining gaps, though it could additionally mention the response structure or the source of slugs.

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 description coverage is 50% (locale has a description, slug does not). The phrase 'by slug' gives the agent a hint that slug is the identifier, but the description does not elaborate on slug format or locale options beyond what the schema already provides. This adds minimal semantic value.

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 a specific verb ('get') and resource ('playbook') with a clear scope ('full text', 'by slug'). It cleanly distinguishes from sibling tool 'academy_playbooks' (which likely lists playbooks) by focusing on a single entity.

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 usage when you have a slug, but it does not explicitly state when to choose this over siblings like academy_playbooks or academy_lesson. No alternatives or exclusions are mentioned, leaving the agent to infer the context.

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