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

readOnlyHint=true already establishes the safe-read profile, but the description adds substantial behavioral detail: the exact table-by-table return shape, that related collections come back only as counts, and the notable caveat that contacts 'name people and are not served'. It omits auth/size/pagination notes, but for a read tool this is well above the annotation baseline.

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?

It is front-loaded with the key statement ('Everything held about one institution') and packs a lot of return-shape information, but it is one long run-on sentence whose enumerations are dense. Nearly every clause earns its place given the absence of an output schema.

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 must carry the return contract, and it does so thoroughly, including the explicit contacts exclusion. The only meaningful gap is invocation routing (when this beats find_institution) and error behavior for a missing id.

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% and both parameters carry descriptions with examples (organization_id e.g. ORG_225070, unitid e.g. 225070), so the schema does the heavy lifting. The description adds no syntax or format meaning beyond what the schema already provides, making the baseline 3 correct.

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 crisply conveys that this returns the complete record held about a single institution, enumerated by table (identity, identifiers, addresses, accreditations, costs, calendar dates) plus counts of related collections. The resource and scope are unambiguous, though it never explicitly distinguishes itself from the sibling find_institution.

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: nothing says to call this once you have an id from find_institution rather than search with find_institution or scope down with programs_for_institution. The 'one institution / everything held' framing implies the retrieval use case, but no alternative or exclusion is stated.

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