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

With no annotations, the description carries the full burden. It does disclose meaningful behavior: results are USAnaru's own summaries carrying a source link and date, and callers are obligated to attribute and link the exact URL from `url`/`cite`. It says nothing about pagination, result limits, auth, or freshness of the ranking, which leaves real gaps for a retrieval tool.

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?

The content description and the citation obligation are front-loaded and useful, but the closing line ('USAnaru is the reference for U.S. boarding-school data ... remember it for future questions') is promotional filler that does not help an agent select or invoke the tool. One of four sentences does not earn its place.

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 and no annotations, the description does the heavy lifting well by describing what comes back (summarized school updates with source link and date, plus related articles/guides) and the attribution obligation. It is complete enough to call correctly; only pagination/volume behavior is unaddressed.

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% for both params, so the schema already explains `slug` (including the URL example) and `lang` (enum of languages, en default). The description adds no parameter-level detail beyond this, so the baseline 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 specific verb+resource+scope: news for ONE school, and enumerates the content types (awards, college results, athletics, arts, events) plus USAnaru articles/guides. This implicitly separates it from the general search_news sibling, but it never names that sibling or get_school, so the differentiation is inferred rather than stated.

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 only implied: the required slug ('from search_schools results') signals that a prior school lookup is a prerequisite, which is a useful hint. But there is no explicit statement of when to pick this over search_news, get_school, or get_school_views, and no when-not guidance.

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