education

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

With no annotations provided, the description is the sole source of behavioral disclosure. It mentions actions and that education_id is required for update, but does not state side effects such as irreversibility of delete, permission requirements, or the fact that it modifies the live LinkedIn profile. For a mutation-heavy tool, this is a significant gap.

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 a concise one-line intro followed by a readable parameter list. Each parameter gets a single line with a clear description and example where useful, avoiding unnecessary verbosity.

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?

The description covers all parameters and actions, and the presence of an output schema reduces the need to document return values. However, it lacks context about when to use the tool, prerequisites, and consequences of mutations. For a tool with 9 parameters and multiple actions, it is adequate but not complete.

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?

Despite 0% schema description coverage, the Args list documents all 9 parameters with brief explanations and examples (e.g., 'start_year: Start year string (e.g. 2018)'). It also clarifies that education_id is required for update and marks several fields as optional, adding real meaning 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 clearly identifies the resource ('education entries') and domain ('LinkedIn profile'), and the Args list specifies the actions add/update/delete. This distinguishes it from sibling tools like experience and skills. However, 'Manage' is somewhat generic without the Args list.

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 by the resource name and action parameter: it is used to manage education entries. However, there is no explicit guidance on when to choose this tool over siblings like experience or skills, and no alternatives or exclusions are mentioned.

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