Dict Educational Institutions

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

With no annotations, the description carries the full burden. "Get" implies read-only and "up to 50 values per request" usefully discloses a batch cap, but nothing is said about missing-id behavior, error semantics, or whether the call requires auth or a specific locale.

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, zero filler. The primary action and its constraint come first, with the id-discovery pointer second.

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 lookup this is close, but with no output schema and no annotations the description should at least indicate what an institution record contains (id, name, and any locale/region fields) or how partial results are handled.

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 0% and the single parameter has no description at all. The description adds the important fact that multiple ids can be supplied (up to 50), but the schema types id as a plain string and the description never explains the delimiter/format for passing 50 values, leaving the key usage detail ambiguous.

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 states a specific verb and resource ("Get educational institutions by id") and scopes the lookup semantics, and it names the sibling that produces the ids. An agent can distinguish it from suggest_educational_institutions without opening either schema.

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?

It clearly routes the agent: use suggest_educational_institutions to discover ids, then call this tool to resolve them. That is real when-to-use guidance, but it stops short of stating exclusions or what happens with unknown/expired ids.

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