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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool 'measures' hiring demand, which implies a read-only operation, but it does not disclose the output format, data freshness, or any limitations. There is no mention of authentication requirements, rate limits, or whether the result is quantitative or qualitative. The description is too high-level to set accurate expectations.

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, compact sentence with no extraneous words. It front-loads the core action ('Measure') and resource, and efficiently adds the data source. It is appropriately sized for the information it conveys.

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?

With no output schema and no annotations, the description alone must equip the agent to understand what the tool returns and any important context. It explains what is measured but not how results are presented, whether they are time-bound, or any caveats. For a measurement tool, this leaves significant ambiguity about the expected output, making the description incomplete for confident invocation.

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 tool has zero defined parameters, and the schema (empty object with additionalProperties: true) imposes no constraints. According to the baseline rule, with 0 params the description does not need to add parameter information. The description does not reference any parameters, which is acceptable given there are none to explain.

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 states a specific verb ('Measure') and a specific resource ('LinkedIn hiring demand and candidate opportunity'), and further specifies the data source ('observed job-listing signals'). This distinguishes it from sibling tools like linkedin_jobs, which likely focuses on listing jobs rather than measuring demand. The purpose is unambiguous and actionable.

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 does not provide any guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or exclusions, nor does it reference sibling tools such as linkedin_jobs. An agent is left to infer that this tool is for measuring demand, but there is no explicit direction about when it is the appropriate choice.

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