careerpulse

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

No annotations are provided, so the description must carry the full burden. It mentions pricing per endpoint but does not disclose other behavioral traits such as authentication requirements, rate limits, data freshness, or what happens on invalid inputs.

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 somewhat verbose, listing all endpoints with pricing, but it uses bullet points and front-loads the general purpose. It could be more concise by omitting redundant details, but it is structured enough for scanning.

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 with no output schema, but the description does not provide usage patterns, examples, or expected responses. The parameter descriptions in the schema are minimal, and the description fails to compensate, leaving significant gaps.

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?

Although schema coverage is 100%, many parameter descriptions are tautological (e.g., 'to', 'from', 'current'). The tool description does not add any further meaning or context for parameters, leaving the agent with minimal guidance beyond parameter 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 the tool is a 'Global career intelligence API' and lists 10 specific endpoints (salary, outlook, etc.), making the purpose well-defined. However, it does not differentiate from the many sibling 'pulse' tools, relying on the 'career' context.

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 is provided on when to use this tool versus alternatives. The description lists endpoints but does not explain how to choose between them or give any usage conditions, exclusions, or prerequisites.

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