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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context the annotations do not: the output is a long full reference (~11k tokens), which warns the agent about context cost before invoking. It does not describe structure or how to navigate the long payload, keeping it below a 5.

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, zero waste: the first front-loads what is returned and its coverage, the second handles routing to the alternative. The size warning is embedded efficiently rather than as a separate sentence.

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?

With an output schema present, 0 parameters, and annotations carrying the safety profile, the description only needs to say what the guide contains and how big it is – both are covered. Nothing an agent needs to decide whether to call it 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 tool takes zero parameters, so per the rubric the baseline is 4. The description correctly implies no input is needed and adds no misleading parameter hints, but there is no parameter content to enrich beyond that baseline.

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?

States a specific verb+resource ('Returns the canonical PayRam headless-agent guide') and enumerates the exact contents (CLI commands, env vars, merchant vs operator mode, wallet flows, adding chains, troubleshooting). This lets an agent distinguish it from the many explain_*/generate_* siblings and from payram_setup_plan without opening any schema.

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?

Explicitly routes the agent to an alternative with a condition: 'For a short personalised plan use payram_setup_plan.' That is clear when-to-use-this-vs-that guidance, but it only addresses one sibling and does not contrast against onboard_agent_setup or the explain_* tools, so it stops short of full coverage.

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