akb_help

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

With no annotations, the description explains the drill-down behavior and that calling without arguments gives an overview. It implies read-only status, which is appropriate for a help 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?

Two sentences, front-loaded with purpose, no redundancy. Every word adds value.

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 help tool with two optional parameters and no output schema, the description covers all necessary usage scenarios (overview vs. drill-down) and parameter constraints.

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 description adds context by listing examples for the topic parameter (categories, tool names, workflows) and clarifying the vault parameter's condition (required for 'vault-skill').

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 it provides help on AKB tools and workflows, with specific instructions on usage (no arguments for overview, drill down into categories/tools). It distinguishes itself from sibling tools as the help entry point.

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?

It explicitly says 'START HERE if you're new to AKB' and explains how to invoke with no arguments or drill down. While it doesn't explicitly say when not to use, the usage is clear and no alternative help tool exists among siblings.

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