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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful provenance ("from the public methodology pages"), which tells the agent the content is public and static. It does not say what happens when a requested section heading is not found, which is the main behavioral unknown.

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, front-loaded with the resource names and ending with the mode semantics, with no filler. The first sentence is dense with nested parentheticals, which costs a little readability but the information is all load-bearing.

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, return values need not be described, and the safety profile is fully covered by annotations. The remaining gap is the free-text section parameter: the description never explains how headings are resolved or what an unmatched heading yields, which matters for a tool whose whole point is partial retrieval.

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?

Schema coverage is 100%, so the baseline would be 3; the description slightly exceeds it by tying the default behavior to the summary format and describing section as "one part" of the page. However, it largely restates the enum descriptions already present in the schema and does not explain how a section heading must be matched (exact string, case sensitivity).

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 names a specific verb ("Explain") and two concrete resources (the Capital Register and the MR Index), and even glosses what each is, so an agent knows exactly what content this returns. It stops short of explicitly contrasting itself with siblings like get_technical_page or get_paper, leaving the agent to infer that this is the methodology-definition 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?

It gives mode-selection guidance (default summary vs. format=full vs. section) which is genuinely useful for choosing how much to fetch. It offers no guidance on when this tool is preferable to sibling tools such as get_technical_page, and no stated prerequisites or exclusions.

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