skills

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Manage skills' and lists arguments; it does not disclose side effects (e.g., idempotency on delete, whether adding an existing skill fails), permission requirements, or rate limits. The description is not misleading but is minimal and adds little beyond what the schema already shows.

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 extremely concise, using only two lines, and structured with an 'Args' block that clearly lists parameters. Every word contributes value; there is no redundant information or filler. It is front-loaded with the main purpose and follows with parameter details.

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 tool is simple (two parameters) and an output schema exists, so return values are likely covered elsewhere. However, for a mutation tool with no annotations, the description lacks any mention of behavioral implications like error conditions (e.g., deleting a non-existent skill) or idempotency. It also fails to provide any usage context relative to sibling tools. The description is adequate for basic invocation but not complete for nuanced decision-making.

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%, meaning the schema provides no descriptions for properties. The description compensates by explaining 'action' as 'add or delete' and giving examples for 'skill_name' ('Python', 'Machine Learning'). This adds meaningful context beyond the raw enum and string types, helping the agent understand the expected values and their semantics.

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 tool's function: 'Manage skills on your LinkedIn profile' with specific actions 'add' or 'delete'. It distinguishes from sibling tools like experience, education, and profile by targeting specifically the skills section of a LinkedIn profile. The scope is clear and unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, edge cases, or when to prefer other sibling tools. The only usage indication is the action parameter, which is more about parameter selection than contextual usage. No explicit exclusion or alternative references are present.

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