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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real behavioral context beyond that: 'Missing history is never estimated' discloses a no-imputation data-quality guarantee, and the ticker:exchange note describes symbol handling. Rate limits and pagination behavior remain undisclosed.

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?

Front-loads the returned data and is reasonably compact, but the unexplained 'Pro:' prefix and the dense run-on list of fields slightly obscure rather than sharpen the message.

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, the field enumeration usefully substitutes for return-value documentation, and the symbol rule covers a key input. But the two pagination parameters go undocumented and there is no guidance on result shape or limits, leaving gaps for a multi-parameter read tool.

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%, so the description must carry all three parameters. It addresses only symbol (omit for company board, ticker:exchange format); limit and offset are never mentioned, and their default/range semantics are left entirely to the bare schema.

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 names the resource (weekly company hiring) and enumerates the data facets it returns: role/seniority/location mix, remote share, surge/freeze signals, peers, retained posting evidence. This makes the tool's content clear, but it never differentiates itself from near-siblings like company.hiring or market.hiring_movers, so an agent cannot tell which to pick from the text alone.

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?

One conditional rule is given ('Omit symbol for the company board'), which is genuine usage guidance for the symbol parameter. However there is no statement of when to use this tool versus company.hiring or market.hiring_movers, leaving the selection decision implied.

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