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

No annotations are supplied, so the description carries the full burden, yet it discloses nothing about what happens on invocation — no indication of what is returned, whether the prompt is static or generated, or whether the query alters output. Instead it offers unverifiable marketing ('Save hours every week') which conveys no behavioral information.

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?

At three sentences it is short, but it is front-loaded with sales copy ('Save hours every week', 'battle-tested', 'No setup') rather than function. The opening sentence spends its most prominent position on a benefit claim that does not help an agent decide or act.

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 prompt/playbook tool with no annotations and no output schema, the description should state the domain, what the agent receives, and how input shapes output. It instead gives a mismatched domain (restaurant/brand growth vs. exam planning) and no return information, so an agent cannot safely invoke it.

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 coverage is 100% and the single optional 'query' parameter is already documented in the schema, so the description is not required to compensate. It adds nothing beyond the schema baseline, which is acceptable here but not additive.

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 name says 'exam-planner' but the description claims to be 'a battle-tested prompt and operating playbook for restaurant/brand growth' — the stated purpose contradicts the tool's own identity and points at a different domain entirely. It does describe a artifact type (a prompt plus playbook), but an agent cannot reliably tell what this tool actually does, nor distinguish it from siblings like exam-kao-gong-pro, cert-exam-route, or brand-fnb-playbook.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance anywhere in the text. 'No setup, works in any LLM chatbot' is a deployment claim, not selection guidance, leaving the agent with no basis to choose this over the many exam-* and brand-* siblings.

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