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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly communicates an informational, read-only behavior: returning a canonical recipe and examples. Since there are no parameters and the tool merely outputs guidance, this is sufficient disclosure of the core behavioral trait; no side-effect or authentication warnings appear necessary for a zero-side-effect 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?

The description is a single, front-loaded sentence that states what the tool returns and when to use it. Every clause earns its place, and there is no redundant or filler content.

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 zero-parameter, informational tool with no output schema, the description is complete. It tells the agent what to expect (a recipe and examples) and when to call it. No additional context is required for correct invocation.

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 input schema has zero parameters specialized 100% by an empty object, so there is no parameter semantics to explain. The rubric baseline for 0 parameters is 4, and the description appropriately adds no redundant parameter detail.

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 ('Return') and a clear resource ('canonical 4-call recipe for buying a server, with examples'). It also distinguishes itself from the sibling server-purchase tools by presenting itself as the meta-help entrance point, so an agent can immediately tell this is not another account, order, or server action tool.

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 explicitly states when to invoke the tool: 'Call this first if you are unsure how to use the tools.' It provides clear contextual guidance, though it does not name specific sibling alternatives or cases where the tool should not be used, which would push it to a 5.

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