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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered and the description carries no contradiction. The description adds only the id-keying note; it says nothing about not-found behavior or what a successful fetch includes, but with annotations present that omission is tolerable.

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 a single short clause with no filler, so nothing is wasted, but it is a verbless fragment rather than a front-loaded sentence. Brevity here shades into under-specification rather than efficient structure.

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 one-parameter lookup with no output schema, the description should at minimum state that it returns one record's details and what happens for an unknown id. Neither is present, so an agent knows the input but not the outcome of the call.

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% with a single required id whose example value is already in the schema, so the description adds little. Its only contribution is naming the id as a 'Datamart id', which hints at the identifier's provenance but gives no syntax or format detail beyond the schema example.

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 fragment "One school site or college campus by Datamart id" identifies the resource (a single school/college record) and the lookup key, which distinguishes it from the sibling education_search. However, there is no verb and the phrasing is elliptical, so the agent must infer that this is a retrieve-by-id operation rather than a filter or list.

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?

No when-to-use guidance is given: nothing says to prefer this over education_search once an id is known, and nothing says to fall back to search when the id is unknown. The description supplies only the scoping fact (lookup is by id), not the decision rule.

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