upsert_education

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

Annotations declare the mutation profile (not read-only, not destructive, not open-world), and the description goes beyond them by disclosing the upsert identity (institution+degree) and the return value. The one gap is that it doesn't state what happens when an existing match conflicts or that the entry is overwritten.

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?

Three compact sentences: purpose+key, routing exclusion, then output. Front-loaded and every sentence earns its place with no filler.

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 5-parameter mutation tool with full schema coverage and no output schema, the description covers purpose, routing, and return. It would be complete at 5 with a note on overwrite/merge behavior when an entry already exists.

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%, so every parameter already carries its own docs including date formats and the bilingual degree shape. The description adds the honesty convention for the degree string, which is real added value, but the rest is schema territory. Baseline 3 with a small lift.

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?

Specific verb (add/change) and resource (education entry), plus the upsert key semantics ('the one with the same institution and degree'). It explicitly distinguishes scope from the sibling set_profile_details, so an agent can route without opening a 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?

Explicit when-to-use ('degrees and formal studies') and an explicit exclusion routing courses/certifications to set_profile_details. Both the condition and the alternative are named.

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