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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds one genuine behavioral hint — that results are sourced per owning node's regional endpoint — but it is cryptic and omits return shape, pagination, or ordering for a list operation with no output schema.

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?

The description is a single short clause with no filler, so it is concise. However, it is a verbless fragment whose second half ('regional door') is unparseable jargon, so brevity comes at the cost of structure rather than through efficiency.

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 one-required-parameter tool with no output schema and no schema descriptions, the description carries the full explanatory burden and delivers almost nothing: no parameter meaning, no usage context, and only a fragmentary hint about regional sourcing.

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% for the single required 'identifier' parameter, and the description says nothing about what the identifier refers to (an issuer, a node, a record) or its expected format. Because coverage is low, the description is expected to compensate and does not.

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 phrase 'Sourced trade and former names' mostly restates the name/title ('List sourced aliases') in expanded form rather than stating a verb+resource action, and no verb ('list') appears at all. The trailing clause 'served by the owning node's regional door' is opaque jargon that adds no discernible scope or distinction from siblings like get_record or resolve_issuer.

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 indication of when to call this tool versus alternatives such as get_record, resolve_issuer, or list_nodes, nor any prerequisite or context guidance. The one hint — that data is 'served by the owning node' — is too vague to route an agent between siblings.

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