get_hiring_signal

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

With no annotations, the description carries the full burden. It discloses the returned metric but does not explicitly mention that it is a read-only operation, how the company filter behaves when null, or any data source/freshness details. It provides minimal transparency beyond the immediate return value.

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 very concise: a one-line definition of the return value followed by a clear parameter note. No unnecessary words, and the primary purpose is front-loaded.

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?

Without an output schema or annotations, the description needs to clarify the return structure. It mentions 'open roles + 30/90-day deltas' but not how these are formatted (e.g., a single number, a dictionary, a list). It also omits the default behavior when the company filter is not provided, leaving ambiguity for an agent.

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 description coverage is 0%, but the description compensates by explaining 'company' as an optional case-insensitive substring filter. This adds meaning beyond the schema, though it does not clarify the behavior when the parameter is omitted or null.

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 the tool returns 'Bitcoin-native hiring velocity (open roles + 30/90-day deltas)' with an optional company filter. This is a specific verb+resource+scope, and it distinguishes itself from sibling tools like get_sovereign_reserves or get_etf_flows by focusing on hiring metrics.

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 purpose is implied but there is no explicit statement of when to use this tool versus alternatives, nor any exclusions or scenario-based guidance. The description only hints at usage through the return value, so it meets the 'implied usage' level.

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