boss_export

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

The description discloses default desensitization behavior and HTML-specific omissions, but does not clarify whether file creation is a side effect or if the tool is read-only. No annotations are provided, so the description only partially covers behavioral traits.

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 two sentences plus an availability line, all front-loaded with the key purpose. Each sentence adds value with no redundancy.

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 the tool has 14 parameters and no output schema, the description only provides high-level purpose and one behavioral detail. It lacks an overview of how parameters work together, such as the interplay between url and other filters.

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 coverage is 100%, so baseline is 3. The description adds no additional meaning beyond what is already in the input schema, such as the relationship between query and url or parameter interactions.

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 exports search results as CSV/JSON/HTML files and supports reusing BOSS直聘 search page URL for filters. It uses specific verbs and resources, distinguishing it from sibling tools like boss_search.

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 exporting search results but does not provide explicit guidance on when to use this tool versus alternatives like boss_show or boss_search. No exclusions or prerequisites are mentioned.

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