help

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It clearly explains that the tool returns "Comprehensive documentation for the requested topic" and lists what each topic covers. It does not explicitly state side-effect-free behavior, but for a help tool this is largely implied.

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 appropriately sized and highly structured: a bold usage directive, a compact bulleted list of topics, and a one-line return statement. Every sentence earns its place, and key guidance is front-loaded.

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 that this is a simple one-parameter help tool with no output schema, the description is complete. It tells the agent when to use it, what topics are available, and what to expect in return. No critical information is missing.

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?

The schema already describes the parameter and its enum, so baseline is 3. The description adds value by explaining what each enum value represents, such as "overview: Summary of all 27 available tools by category" and "workflows: Common multi-step workflows for typical tasks," going beyond the bare enum names.

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 the tool's purpose: "Get comprehensive help about ANTLR4 MCP tools, common workflows, and usage examples." It uses a specific verb (get help) and resource (ANTLR4 MCP tools), effectively distinguishing this meta-tool from the many grammar-manipulation sibling tools.

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 gives explicit usage guidance: "USE THIS TOOL FIRST when starting work with ANTLR4 grammars." It also enumerates the available topics and suggests "overview" for a general introduction, which helps the agent choose the correct starting point.

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