add_linkedin_education

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

No annotations are provided, so the description carries full burden. It only states 'Add education', which implies a write operation, but fails to disclose necessary permissions, rate limits, side effects (e.g., authorization requirements, idempotency), or error conditions. The description offers minimal behavioral insight.

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 single sentence that is concise and front-loaded. It contains no redundant or extraneous information, earning the highest score for efficiency.

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 mutation tool with 9 parameters (only 1 required), the description lacks completeness. It does not explain return behavior, validation rules, or error handling. Given no output schema and no annotations, the description should provide more context about the operation's outcome and prerequisites.

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 input schema covers all 9 parameters with descriptions (100% coverage), so the baseline is 3. The description adds no additional meaning beyond 'add education'; it does not explain parameter relationships, defaults, or constraints beyond the schema. A neutral score is appropriate.

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 the action: 'Add education to your LinkedIn profile', with a specific verb and resource. It effectively distinguishes from sibling tools like add_linkedin_certification or add_linkedin_position by focusing on the education domain.

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 implies the tool is used to add an education entry, but it lacks explicit guidance on when to use it versus alternatives (e.g., update_linkedin_position for editing). No when-not-to-use or prerequisites are mentioned. The context is clear but not comprehensive.

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