Instaffo: set skill experience

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

The description explicitly states the write behavior ('This writes to your real profile') and the preview mode, adding significant behavioral context beyond the openWorldHint annotation. There is no contradiction with annotations.

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 three focused sentences with no waste. It front-loads the purpose, then adds key specifics. Every sentence adds value.

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 the core functionality and preview behavior. It does not explain the preview response format, but an output schema exists. The mention of skill UUID source is in the schema but not description, which is a minor gap. Overall complete for the tool's 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?

The description adds critical meaning: 'Durations are 0-5 (5 means 5+).' and explains the confirm parameter's effect. With only 50% schema description coverage, the description compensates effectively by clarifying value ranges and behavior.

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: 'Set your years-of-experience for one or more skills on your profile.' It uses a specific verb ('Set') and identifies the resource ('skills on your profile'). No sibling tool performs this action, so it distinguishes well.

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 guidance on when to use the confirm parameter ('Without confirm=true it returns a preview') and advises to submit truthful values. It doesn't explicitly mention alternatives because no alternatives exist among siblings. Context is clear, but could add prerequisites (e.g., skill UUIDs from job screening data).

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