boss_stats

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

The description discloses the read-only and aggregate nature, and lists the data sources. With no annotations, this adequately sets expectations, though more detail on output format would improve it.

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 plus an availability note, front-loading the key purpose and constraints. It is concise, but separating the availability into a structured field might be clearer.

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?

Given no output schema, the description lists aggregated data types but not the output format or structure. This is acceptable for a simple tool but lacks completeness for complex use.

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 single parameter 'days' is fully described in the schema (100% coverage) with 'statistics window days'. The tool description adds no further semantics, so baseline 3 is appropriate.

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 provides 'delivery conversion funnel statistics' with a read-only aggregate of greetings, deliveries, candidate pool, and monitoring data, which distinguishes it from other boss_* tools like boss_search or boss_resume_list.

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 availability note specifies roles and platforms, guiding when to use (candidate on zhilian or zhipin) and implicitly when not (recruiter or other platforms). However, no explicit comparison to sibling tools is given.

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