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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds genuine value by disclosing what is returned (row, affiliated institutions, sharing origin, program count). It does not mention return size, pagination, or auth requirements, so it goes beyond annotations but not richly.

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, front-loaded with the resource being fetched, with each clause adding a distinct piece of return information. Efficient, though it reads as a noun phrase rather than a directive sentence.

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 the return shape, and it does so by naming the main components returned. For a single-entity lookup this is nearly complete; finer field details would require the response itself.

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 the single parameter is self-documented with a source hint ('from find_catalogs'). The description adds no additional parameter semantics, so the baseline 3 is appropriate.

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 specifies the resource (one catalog edition) and enumerates its contents — row, institutions that use it, sharing source, and program count. This lets an agent distinguish it from find_catalogs, the plural finder. It lacks an explicit verb ('get'/'retrieve'), but the resource is unambiguous.

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 explicit when-to-use or when-not-to-use statement in the description. Usage is only implied by the schema's 'A catalog id from find_catalogs', which suggests the intended find_catalogs → get_catalog pipeline. Adequate but leaves the alternative unpinned.

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