Add Education

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

The description adds behavioral constraints beyond annotations: 'Dates must be accurate' and 'Do not fabricate or embellish information.' Annotations only show readOnlyHint=false and destructiveHint=false, so the description provides useful context about data integrity.

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 sentences, each serving a distinct purpose: action, pre-check, and data quality. No redundant information; front-loaded with the core action.

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 creation tool with 8 parameters and no output schema, the description covers pre-conditions (duplicate check, data completeness) and ethical constraints (no fabrication). It lacks details about success response, but that is acceptable given no output schema.

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 100% with descriptions for all 8 parameters. The description adds general context about handling incomplete data but does not significantly enhance individual parameter meaning beyond what the schema already provides.

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 'Add an education entry to the user's profile' with a specific verb and resource. It distinguishes from sibling tools like get_education, update_education, and delete_education.

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?

Explicitly instructs to check existing education with get_education to avoid duplicates and to ask the user to fill in missing information if the source is incomplete. Provides clear when-to-use and 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.