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

The annotations already declare a safe, read-only, idempotent, open-world operation. The description adds useful provenance and return content (tasks, outlook, typical education), but does not go beyond schema/annotations to cover rate limits, authentication needs, or error behavior.

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 short and front-loaded, moving from the core resource to data source to an invocation example. The example is useful but partly duplicates the schema's own examples, keeping it just short of highly efficient.

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?

For a simple three-parameter read-only lookup with full schema documentation and no output schema, the description gives adequate context by naming the data source and the kinds of occupation details returned. It is complete enough for correct invocation, though it could better explain the optional location parameter's impact.

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 100%, so all three parameters, including the optional location parameter and its default, are already documented in the input schema. The description adds no parameter meaning beyond the schema and does not mention how location affects results.

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 resource and scope: occupation detail covering tasks, outlook, and typical education, sourced from CareerOneStop / O*NET. It clearly distinguishes the tool from the sibling salary tools by focusing on occupation data rather than salary or comparison, though it does not explicitly name those alternatives.

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 implies the tool is used to retrieve occupation details for a given occupation, but it gives no explicit when-to-use guidance, no when-not-to-use exclusions, and no routing to sibling tools such as careeronestop_salary or careeronestop_compare_salary.

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