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

The annotations already establish read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds a useful architectural trait — that the record is served by the owning node's regional door and never held at the apex — but says nothing about auth needs, error behavior, or what happens when the identifier is 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?

A single front-loaded sentence that begins with the verb and resource before adding nuance. It is appropriately sized, though the parenthetical about the apex is niche jargon that earns its place less clearly than the first half.

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 no output schema and 0% parameter coverage, the description carries the full burden of explaining the return shape and how identifier/version resolve. It does neither, and the appeal to node topology does not tell the agent enough to call the tool correctly.

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 description coverage is 0%, and the description mentions neither the required identifier nor the optional version. The word "full" hints that no projection is applied, but that does not compensate for two completely undocumented parameters.

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 ("Return") and resource ("the full Capital Markets Record"), which is enough to distinguish it from the list_* and resolve_issuer siblings. However, it never explicitly contrasts itself with those siblings, and the second clause about the "regional door" and "apex" is jargon that obscures rather than clarifies.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the sibling tools a caller might reach for instead. The agent must infer the usage context purely from the name.

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