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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds provenance the annotations cannot (Federal Reserve NIC, ffiec.gov/npw) and the full record contents, but says nothing about not-found behavior or whether a mismatched identifier errors.

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?

Front-loaded with the payload contents, then the identifier options, then the fallback workflow. Dense but zero filler; every clause aids selection or invocation.

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 compensates by enumerating the fields returned, and it covers provenance, identifier options, and the prerequisite search path. Nothing material for a read-only lookup is missing.

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 100% and each parameter already documents the exactly-one constraint and the pack it chains to, so the description largely echoes structured data. The 'join key shared with the fdic/gleif packs' framing adds mild routing value but no new syntax or format beyond the schema.

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+resource ('Full NIC record for one institution') and enumerates the returned fields (legal name, FDIC certificate, LEI, institution type, charter type, location, status). It also distinguishes itself from the sibling nic_search_institutions, so an agent can separate lookup-by-ID from search-by-name.

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?

Explicitly names the three accepted identifiers and the exact-one constraint, and routes the agent: 'Use nic_search_institutions first to find an RSSD ID from a name.' When-to-use and the alternative are both stated.

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