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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds data provenance (FDIC Institution Directory + NIC), which is genuine context, but it does not say whether 'branches' means a count or a per-branch list, nor how stale the data may be.

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 compact sentence lists the returned attributes first and the provenance last, so the useful part is front-loaded. It is terse to the point of being a label rather than a sentence with a verb, but no words are wasted.

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, the description carries the burden of explaining what comes back; the field list partially serves as that, but it is not clearly framed as the return shape. For a one-parameter read tool this is minimally adequate rather than complete.

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 schema has full description coverage for the single rssd_id parameter, including an example, so it does the work here. The description adds no meaning beyond the schema, which is the expected baseline when coverage is 100%.

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 enumerates the specific data the tool returns (charter type, primary regulator, holding company chain, branches), which is concrete enough to know it is a corporate-structure lookup. It stops short of a verb and never distinguishes itself from the sibling 'structure_full', so an agent cannot tell which to pick from the text alone.

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 or when-not-to-use guidance, no mention of prerequisites, and no reference to alternatives such as 'structure_full' or 'branches', even though an agent must choose between them. The reader can infer it is a per-bank lookup only from the required RSSD id in the schema.

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