akb_help

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

As a help tool, it is implicitly read-only, but lacks explicit statement of no side effects. The description discloses the behavior of calling with no arguments, which is helpful. No annotations present, so description carries the burden.

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?

Three sentences, front-loaded with purpose, and no extraneous information. Every sentence earns its place.

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?

Given it has only 2 optional params and no output schema, the description effectively covers the main usage patterns. It is complete and clear for a help tool.

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 description adds value by explaining how to use 'topic' (categories, tool names, workflows) and 'vault' for vault-skill. This goes beyond the schema's basic descriptions.

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 guidance on starting with no arguments. It distinguishes itself from sibling action-oriented tools by being a 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?

Provides clear usage instructions: no arguments for overview, drill down into categories or specific tools. 'START HERE' implies it's the first tool to use, but does not explicitly exclude use cases or mention alternatives.

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