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

Beyond the annotations, it discloses upsert semantics, partial-update behavior ('changing only the fields you send'), and the create-only requirement for institution. It also instructs the agent to confirm dates and not fabricate, which are important behavioral guardrails for a user-facing write.

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?

Four sentences, with the core action and modes front-loaded in the first sentence. Each subsequent sentence adds either a workflow condition or a data-quality guardrail; 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 9-parameter upsert with no output schema, the description plus schema covers creation vs update, required fields, duplicate avoidance, date handling, and what to ask the user. No critical calling behavior is left unexplained.

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?

The schema covers 100% of parameters, so the baseline is 3. The description adds contextual guidance on id/institution usage and tells the agent to ask about degrees/bootcamps/certifications and confirm dates, which enriches but does not fundamentally extend 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 'Add or update an education entry (upsert)' – a specific verb and resource, with the two modes spelled out. The 'education' resource distinguishes it from siblings like save_work_experience, so an agent knows exactly what it targets.

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?

Directs the agent to 'Check get_profile first to avoid duplicates' and to source ids from get_profile, giving a clear precondition and workflow. It does not explicitly name an alternative tool for the same operation or list exclusions, so it stops short of full when-not-to-use guidance.

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