add_education

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

With no annotations provided, the description carries the full burden. It discloses the scope (locked to authenticated account) and that this is a write operation. But it does not state whether the credential appends to existing education entries, replaces anything, or what happens if the session is invalid. The description provides minimal behavioral context but leaves several questions unanswered.

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?

The description is efficiently structured: a one-line purpose, a one-line security notice, and a terse bulleted argument list. Every sentence adds information, and the format makes the parameter semantics easy to scan.

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 10-parameter mutation tool with no annotations and an output schema available, the description covers the purpose, scope, and all parameters sufficiently. It could still mention whether the education entry is appended vs. replaced and what validation is applied to month/year values, but the core invocation information is present.

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 0%, so the description must compensate. It fully does: every parameter is given a clear plain-language meaning and an example, and optionality is explicitly marked for grade, activities, and description. This is high-value documentation beyond the raw 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 opens with a specific verb and resource: 'Add an education credential to your own LinkedIn profile.' This clearly differentiates the tool from siblings like add_experience and add_skill, and the security notice further defines the scope as the authenticated account.

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?

The description clearly implies when to use it—when adding an education credential to the user's own profile. However, it does not explicitly mention when not to use it or name alternative tools for different profile sections, so it lacks the explicit exclusions needed for a 5.

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