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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful behavioral context by enumerating the categories of data the response will include (tools, identifiers, citation rules, languages, licence, bulk-ingest URLs), which is valuable beyond the annotations. It does not contradict any annotations.

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 short sentences with no filler. The entry-point instruction is front-loaded, and the second sentence packs the high-value detail about return contents into a compact list. Every word earns its place.

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 overview tool with an output schema available, the description is complete. It clearly states what the agent will get and why to call it first. An output schema handles detailed return-value structure, so the description provides enough context 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 tool accepts 0 parameters and the schema description coverage is 100% (trivially, since there are no properties). The description does not need to add parameter semantics, and with no parameters the baseline of 4 is appropriate.

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 and resource: 'Get the complete MCP map' and identifies exactly what will be returned (five-domain core, Article, Labs, Homeric Atlas, claim-registry surfaces, tools, identifiers, citation rules, languages, licence, bulk-ingest URLs). It clearly distinguishes this from the many sibling get_* tools by framing it as the global map and 'start here' entry 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 phrase 'start here' explicitly signals this is the intended entry point for an agent, providing clear usage context. It does not list alternatives or exclusion criteria, but given the unique overview role and 0 parameters, the guidance is sufficient.

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