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

Beyond the readOnly/idempotent annotations, the description discloses the output semantics: a numeric score range (-100..+100), the five band values, and the interpretation of momentum as acceleration/deceleration. It does not discuss edge cases like unknown skills, but the safety profile is already covered by 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?

A single sentence front-loads the core comparison, then lists the return shape and the business meaning. Every clause earns its place with no repetition or filler.

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 one-parameter read-only tool, the description gives the score range, band taxonomy, and interpretation, which is enough to invoke and understand the result. The main missing detail is the exact definition of 'recent vs prior period' and acceptable skill input values, but these are minor for this complexity level.

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?

The schema only states that skill is a required string with 0% description coverage. The description adds the meaning that this is the skill whose hiring demand is being measured, which maps the parameter to its purpose, but it does not specify accepted skill names, formats, or examples.

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 a comparison of recent vs prior period demand for a skill and specifies the returned score range and band labels, so an agent can tell it is a momentum metric. It does not explicitly name a sibling alternative (e.g., jobs_skill_trends), so it stops short of the strongest differentiation.

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 when to use it: when you want to know whether hiring demand for a skill is accelerating or decelerating. However, it gives no exclusions or explicit alternatives, and with many jobs_* sibling tools the selection logic is left to inference.

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