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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds meaningful context beyond the annotations: it specifies the structure of what comes back (ranked contact categories, ready searches, current top employers, named people from public posts) and discloses 'Nothing sent is stored,' which is useful privacy information not present in the structured fields.

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 core purpose is front-loaded, but the long parenthetical list of contact types and the run-on final sentence make it denser than it needs to be. Every element is relevant, yet the middle listing could be tightened without losing information, so it reads as adequate rather than crisp.

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?

For an 11-parameter tool with full schema coverage and no output schema, the description covers the essentials an agent needs: what it produces, the shape of the result (ranked categories, searches, employers, named people), and a privacy note. The main omission is routing guidance against the many sibling jobspotter tools, which keeps it from a 5.

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 description coverage is 100%, so every one of the 11 parameters is already documented in the schema, which sets the baseline at 3. The description only restates the input at a high level ('from a CV or a few details and the role wanted') and adds no syntax, format, or required-vs-optional nuance beyond what the schema provides.

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 states a specific verb and resource: it produces a ranked list of who to network with, generated from a CV plus the target role. It even enumerates the kinds of contacts it returns (hiring managers, recruiters, alumni, etc.), which makes the output concrete. It stops short of naming or contrasting with close siblings such as jobspotter_find_people or jobspotter_hiring_posts, so differentiation is implied rather than stated.

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 quoted example questions ('who should I network with?', 'how do I get a job as a data scientist without applying cold?') convey the intended situation and give real context for when to call it. However, there is no explicit when-not guidance and no routing to alternatives like find_people, so an agent must infer the boundary itself.

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