linkedin_answers_bank

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool both reads and mutates the answer bank, but says nothing about permissions, reversibility, whether 'set' overwrites or merges, or what a read returns. For a mutation-capable tool with zero annotation coverage 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?

Two sentences, front-loaded with the verb+resource and a brief rationale. No filler, though the second sentence is more persuasion than information.

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?

A 4-parameter mutation tool with no annotations, no output schema, and an action enum with four undocumented modes. The description leaves the agent unable to determine how to invoke set-profile vs set-resume vs set, or what read returns, which is inadequate for this complexity.

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 only 25% (solely the 'entries' param is annotated), so the description must compensate but does not. It never explains the action enum values, nor the label/value pairing convention, nor how 'set-profile'/'set-resume' differ from plain 'set'. The content examples hint at possible labels but do not map to parameters.

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 states a specific verb pair ('Consulta o edita') and a concrete resource ('banco de respuestas que se reutiliza al postular'), then enumerates example contents (contact data, experience, availability, default CV). An agent can tell it apart from sibling tools like linkedin_job_apply or linkedin_profile_edit, but the description does not name any siblings explicitly.

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?

There is no explicit when-to-use guidance or any statement about which action to pick (read vs set vs set-profile vs set-resume). The closing sentence ('Cuanto más completo, menos se atascan las postulaciones') is motivational advice, not routing guidance. Usage is only implied by the relationship to applying.

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