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

No annotations are provided, so the description carries the full burden. It usefully discloses the billing behavior ('1 credit if found'), which implies no charge when nothing is found, but it does not state what is returned on a miss (error vs. empty result) or any rate limits or auth needs.

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?

Two short sentences with no waste; the resource scope is front-loaded and the credit cost follows immediately. Nothing needs trimming or reordering.

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 simple one-parameter read tool with no output schema and no annotations, the description covers the accepted input forms and the cost model. The main remaining gap is the return payload shape and miss behavior, which is a minor omission at this complexity.

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%, so the single 'identifier' parameter is already documented. The description restates the accepted identifier forms (LinkedIn URL, slug, numeric ID) without adding format examples or normalization rules beyond the schema, so the baseline of 3 applies.

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 concrete verb ('Get') and a specific resource ('a school or university'), which distinguishes it from the sibling enrich_company and enrich_person tools by subject type. It does not explicitly name those siblings, but the resource noun makes the scope 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?

Usage is implied: use this when you have a LinkedIn school URL, slug, or numeric ID and need school data. There is no explicit statement of when not to use it, no mention of the alternative enrich tools, and no prerequisites such as authentication requirements.

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