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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful detail that results land in SOC 2018 occupations and GWIX roles, but says nothing about pagination, output shape, or what happens when a code maps to nothing. Modest added value against an already-rich annotation set.

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 'Use for:' trigger, no filler. The only inefficiency is the slightly tangled second sentence describing the mapping output.

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?

No output schema exists, so the description must carry return-value meaning; it does indicate the output is SOC 2018 occupations and associated GWIX roles. For a read-only crosswalk tool with 2 required params, that is close to complete, missing only failure/empty-result behavior.

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 coverage is 75% and the description reinforces the from_system enum values and the two mapping targets (SOC 2018 and GWIX roles). It adds directional meaning beyond the bare enum, though to_system defaults and roles_limit behavior are left to the schema.

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 names a specific verb (map) and resource (occupation codes) and lists the source taxonomies (soc_2018, soc_2010, onet_soc, isco_08, esco) plus GWIX roles. It is clearly distinct from the ID/lookup siblings. The second sentence muddies direction slightly by mixing 'maps to SOC 2018' with 'GWIX roles their ads fall in', keeping it from a clean 5.

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 'Use for:' framing gives explicit when-to-use criteria ('what is this SOC/O*NET/ISCO/ESCO code in another taxonomy', 'which occupation codes a job maps to'). No alternative tool is named, but none of the listed siblings performs code crosswalking, so context is sufficient without exclusions.

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