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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint false, covering the safety profile. The description adds a cryptic 'Demo mode' behavior but does not clarify what demo mode is or when it applies. No contradiction exists, but the added context is minimal and vague.

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 appropriately short and the main verb phrase is front-loaded. The second sentence about demo mode is terse and ambiguous, introducing slight uncertainty, but overall the description is efficiently sized with no 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 one-parameter, read-only tool with annotations covering safety, the description is mostly adequate. However, with no output schema, it does not explain the shape of 'trend rows' or clarify the demo mode limitation, leaving gaps for an agent that needs to interpret results or know whether a requested skill is supported.

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 fully covers the sole `skill` parameter with an example ('python'), so the description adds little beyond the schema. The phrase 'selected sample skills' hints that some skill values may be limited in demo mode, but it does not specify valid values or how demo mode is triggered.

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 clear action ('Return') and a specific resource ('job and skill-demand trend rows'), so an agent can tell it produces trend data. However, it does not explicitly differentiate itself from sibling tools like jobs_remote_trends or jobs_skill_graph, relying on the name and generic phrasing.

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?

No guidance is provided on when to use this tool versus the many jobs_* siblings. 'Demo mode allows selected sample skills' hints at behavior but does not explain the intended use case or exclusions. The agent must infer when this tool is the right choice from the name alone.

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