Skill Impact

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

Annotations provide readOnlyHint=true; description confirms it's a simulation ('simulate adding it') with no mutation. Details output fields (newJobsUnlocked, boostedJobs, etc.) and profileCompleteness, adding significant behavioral context beyond 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?

Four sentences, all informative with clear flow: purpose, output, usage examples. Slightly verbose but every part earns its place.

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?

Given 0 parameters, no output schema, and 100% schema description coverage, the description fully explains tool behavior, return fields, and profileCompleteness use case, leaving no gaps.

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?

No parameters (0 params, schema coverage 100%), so baseline is 4. Description correctly implies no inputs are needed, and adds no conflicting parameter details.

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?

Description uses specific verb 'simulate adding' and resource 'skills the authenticated user does NOT have', clearly distinguishing from sibling tools like skill_gap. Provides concrete output fields.

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?

Explicitly states use cases ('what should I learn next?', 'which skill would unlock the most jobs?') and mentions 'Pro tier' as a constraint. Does not explicitly exclude alternatives, but context of sibling tools makes it clear.

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