get_hiring_signals

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

Without annotations, description provides minimal behavioral info: it fetches recent signals. It implies read-only but doesn't state side effects, output size, or error handling.

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?

Single concise sentence, no redundant words.

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?

Tool is simple, but no output details or usage guidance. Missing clarification on limit and no comparison to siblings. Overall adequate but not comprehensive.

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 has no descriptions. Explanation clarifies 'ticker' (one ticker) but leaves 'limit' undefined. Both are required, so an agent may not know what limit controls.

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?

States a specific action (fetch) and resource (headcount/hiring signals) for a single ticker, clearly distinguishing it from sibling tools like list_companies or get_financials.

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 explicit guidance on when to choose this over alternatives; relies on the name to imply purpose. Lacks conditions or comparisons.

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