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

No annotations are provided, so the description carries the full burden. It adds the behavioral context that data is 'refreshed from company job boards', implying periodic updates. However, it does not mention ordering, pagination, rate limits, or other operational behaviors.

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 a single, front-loaded sentence with no filler. It states the purpose, target industries, and data source efficiently, earning high marks for conciseness and structure.

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 tool is simple (2 params, no output schema), and the description gives enough context for basic invocation and selection. It lacks output format details and limit semantics, but for a list tool, the description is largely adequate.

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 50% (industry documented, limit not). The description reinforces the industry parameter by listing specific categories, but does not explain the 'limit' parameter's semantics, default, or constraints. It provides some added meaning but leaves a key 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 uses a specific verb ('list') and resource ('design/UX/HMI roles at frontier companies'), and adds scope (defense, robotics, etc.) and data source (company job boards). This clearly distinguishes it from broad sibling tools like 'search'.

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 for fetching current design job listings, but provides no explicit 'when to use' guidance, alternatives, or exclusions. Sibling tools like 'search' could be an alternative, but no differentiation is offered.

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