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

There are no annotations, so the description must carry the burden. It usefully discloses what information the call returns (boards, auth, MCP url, rate limits, feed modes), but it does not state whether the call is read-only, requires authentication, or returns structured JSON versus an explanatory text format.

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?

A single, information-dense sentence with no filler. The main purpose is front-loaded, and the list of covered topics is compact yet comprehensive.

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 discovery call, the description gives enough to understand what the tool will explain. However, with no output schema and no annotations, it stops short of specifying the response shape, return format, or any prerequisites, leaving some ambiguity about exactly what the agent will receive.

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 has zero parameters and the schema is empty, so there is no parameter information to clarify. The description does not need to add parameter semantics; the no-parameter baseline applies.

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 clear scope ('the whole site') and enumerates the exact information domains (boards, auth, MCP url, rate limits, feed modes). This distinguishes it from narrower siblings like list_boards and whoami, making the purpose immediately understandable.

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 phrase 'One call that explains the whole site' provides clear context that this is the top-level discovery call, meant to give an overview before using more specific tools. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to make a sensible selection.

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