careerpulse

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

No annotations provided, and the description does not disclose behavioral traits such as authentication requirements, rate limits, or side effects. It only mentions per-endpoint pricing. For a tool with no annotations, the description should provide more behavioral context.

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 front-loaded with the main purpose but becomes verbose with a list of 10 endpoints including pricing. While informative, it could be more concise by summarizing or structuring as a bullet list.

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 tool has 18 parameters and 10 actions but the description does not link which parameters are relevant for each action. No output schema or usage examples are provided, leaving the agent uncertain about which parameters to use for a given endpoint.

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% with descriptions for all 18 parameters, but many descriptions are just the parameter name (e.g., 'title', 'current', 'target'). Some parameters have useful details (e.g., lang, location, tenure), so overall the description adds marginal value beyond the schema names.

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 it is a global career intelligence API serving 3.5 billion workers, with specific endpoints for salary, outlook, skills-gap, etc. This verb+resource pairing is explicit and distinguishes it from sibling tools like talentpulse or marketpulse.

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 guidance on when to use this tool versus alternatives. The sibling list includes many similar 'pulse' tools (e.g., talentpulse, prospectpulse) but the description does not differentiate or provide when-to-use/when-not-to-use advice.

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