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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that it returns a map with specific contents, but since an output schema exists and there are no side effects, the description does not go beyond what annotations and schema already establish.

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, front-loaded sentence begins with the key directive 'Get the complete MCP map — start here' followed by a compact list of contents. Every word contributes meaning, with no wasted elaboration.

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, read-only, idempotent tool with an output schema, the description fully covers what the agent needs to invoke it correctly. The scope of the returned map is described succinctly and completely.

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, so the description carries no parameter burden. The baseline for a no-parameter tool is 4, and the description appropriately stays silent on inputs.

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 states a specific verb and resource: 'Get the complete MCP map' and explicitly lists what it returns (five-domain core, surfaces, tools, identifiers, citation rules, languages, licence, bulk-ingest URLs). It clearly differentiates this umbrella tool from the entity-specific get_* and list_* siblings by framing it as the comprehensive starting 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?

The description explicitly says 'start here,' which tells the agent this is the intended entry point for orientation. It does not name alternatives or state when not to use it, but for a zero-parameter overview tool the directive is clear enough.

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