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

No annotations are provided, so the description must disclose behavioral traits. It mentions that the unit of assessment is the task, which is a useful clarification, but it omits other important behaviors such as whether the result is a list, pagination, error conditions, or side effects. The description is too sparse to fully inform an agent about the tool's 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 two sentences with no wasted words. The first sentence states the core purpose, and the second adds a relevant behavioral nuance. However, it is too terse given the tool's complexity, but as a standalone text it is concise and front-loaded.

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 tool with no output schema, no annotations, and two undocumented parameters, the description is severely incomplete. It does not explain the parameters, return format, usage context, or how it relates to other occupation-related tools. An agent would struggle to call it correctly without additional information.

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% and the description provides no explanation for the two parameters, 'slug' and 'locale.' The agent must guess what 'slug' refers to or how locale affects results. The description completely fails to compensate for the schema gap.

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 identifies the resource as 'task breakdown for one occupation,' which matches the tool name and implies the return of task data. It distinguishes it from siblings like get_occupation by focusing on tasks rather than job details, though it does not explicitly name a sibling. The unit-of-assessment note adds clarification but does not fully differentiate from all 16 siblings.

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?

There is no guidance on when to use this tool versus alternatives. The description offers a semantic caution ('unit of assessment is the task, never the job title') but does not specify contexts, prerequisites, or exclusions. With a large sibling set, explicit routing or conditions are absent.

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