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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new operational context: the $0.25 USDC x402 payment cost, which an agent must know before calling a paid endpoint. It does not mention throttling, failure modes, or lookup ambiguity handling, keeping it below a 5.

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?

Front-loaded with the lookup purpose, then the return-field inventory, then use cases, then price — a sensible order. The long comma-separated field list is dense but earns its place given there is no output schema. Slightly heavy but no filler sentences.

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's enumeration of returned fields is the only signal of what an agent gets back, and it covers that well; the pay-per-call cost is also disclosed. Remaining gaps are minor — no note on partial matches, unknown institutions, or whether incomplete records return nulls.

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%, with the 'lookup' parameter having an example ("Ohio State") and 'language' enumerating all 16 accepted codes — the schema does the heavy lifting. The description adds no syntax guidance for the lookup string (fuzzy vs exact, abbreviation handling) or extra meaning for the language parameter.

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 and resource — 'University and college lookup' — and enumerates exactly what comes back (official name, location, type, founding year, enrollment, tuition, endowment, conference, programs, website). No sibling in the long Interzoid catalog covers higher-education institutions, so an agent can disambiguate from business_info, city_standard, or country_info on the resource alone.

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?

Names concrete use cases — education research, admissions tools, and enriching student, alumni, and recruiting records — which gives a clear selection context. It stops short of when-not to use it or naming an alternative (e.g. company enrichment via interzoid_business_info), so it is context-rich but not exclusionary.

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