uis_country_education_profile

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

Annotations already provide readOnlyHint and idempotentHint. Description adds that it returns a Markdown profile with specific indicator types, but no additional behavioral details (e.g., no mention of side effects, auth, or rate limits).

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?

Concise with short bullet list of indicators, clear Args and Returns sections. Efficient use of space, no fluff.

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 an output schema present, the description adequately covers the tool's purpose and return format (Markdown profile). No major gaps, though edge cases like missing data could be addressed.

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 descriptions already cover parameter details (country_code format, latest_year_only toggle). Description adds value by listing the types of indicators included (literacy, enrollment, etc.), which aids understanding beyond schema.

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 clearly states it creates a comprehensive education profile for a country using UNESCO UIS, listing specific indicators. It distinguishes from sibling tools like uis_get_education_data (raw data) and uis_compare_countries (comparison).

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?

Implied usage for obtaining a full country profile, but no explicit guidance on when to use vs alternatives (e.g., uis_get_education_data for raw data). No when-not-to-use or prerequisite conditions.

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