validate_profile

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

With no annotations, the description carries the full burden. It discloses the return shape (validation status, cleaned data, warnings) and that the input must be a JSON string, but says nothing about failure behavior, whether the profile is mutated, or any permission requirements.

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-loads the purpose in the first sentence, then uses a tidy Args/Returns layout. Slightly verbose with the multi-line arg wrapping, but every part conveys information.

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?

An output schema exists, so return values needn't be spelled out, yet the description still summarizes them. For a single-parameter validation tool the purpose, input source, and outcome are all covered, leaving only workflow placement and error semantics 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 coverage is 0%, so the description must compensate, and it does: it explains that profile_json is a JSON string of the extracted profile and that it must match the structure returned by get_extraction_schema. That is meaningfully more than the bare 'Profile Json' title in the 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?

States a specific verb (validate) and resource (extracted institution profile) and names exactly what it validates against (Pydantic schema and WHED database picklists). This clearly separates it from siblings like save_profile and get_extraction_schema, though it stops short of explicitly contrasting them.

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 implied: it references get_extraction_schema as the source of the required structure, which hints at the workflow order (extract, then validate). However, there is no explicit statement of when to call this versus save_profile, nor any when-not guidance.

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