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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows the tool is safe and read-only. The description adds the fact that data is 'Collected daily by Gloomberb,' which gives freshness context. It does not mention any limitations, rate limits, or response format. Since annotations cover the safety profile, the description provides marginal additional value beyond them.

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 sentence that front-loads the core action ('Read one company's hiring picture') and then lists the key data dimensions. It is efficient and not verbose, though the enumeration is a bit dense with commas and 'and.' It is appropriately sized for the tool's complexity.

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 description gives a good overview of the output categories (open roles, function, country, seniority, posting age, pay ranges, theme signals, newest roles), which is helpful given there is no output schema. However, it does not explain the 'roles' parameter's effect on the output, nor does it mention any pagination or data structure details. While it covers the main dimensions, it leaves a gap around parameter behavior, so it is only partially complete.

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 50%: only 'ticker' has a description. The 'roles' parameter is left undefined in both the schema and the description. The description mentions 'open roles' but does not explain what the 'roles' parameter controls (e.g., number of roles returned). With half the parameters undocumented, the description should compensate, but it does not, leaving the agent to guess the semantics of 'roles'.

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 specific verb ('Read') and a specific resource ('one company's hiring picture from its own careers system'), then enumerates the data dimensions (open roles, hiring by function, country, seniority, posting age, pay ranges, theme signals, newest roles). This clearly distinguishes it from siblings like company.profile (general info) and market.hiring_movers (market-level movers), so an agent can immediately tell what this tool does and what it is not.

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 usage for a single company's detailed hiring data, but it does not explicitly state when to use this tool versus alternatives or when not to use it. For example, it does not mention 'for market-wide hiring trends, use market.hiring_movers instead.' The context is clear enough to infer the primary use case, but there is no explicit guidance on exclusions or alternative selection.

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