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

With no annotations, the description carries full burden. It does disclose useful behavior beyond the schema: data is LIVE, every field carries data_as_of, and jev:true with typesafe_key adds exactly ONE calibrated ranking. It does not, however, state whether the call is read-only, whether it needs auth, or how many suggestions are returned.

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?

Two dense sentences, front-loaded with what gets suggested, and no filler. The density of internal jargon ('harvester vocabulary', 'TypeSafe/Jev ranking') makes it slightly hard to parse but the structure is tight.

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 a six-parameter tool with no output schema and no annotations, the description omits too much: how task is used, what api_key/chain_id do, whether this is read-only, and what the response looks like. It covers data provenance well but leaves the call contract substantially under-specified.

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 only 17% (six parameters, essentially undocumented), so the description must compensate and it largely does not. It explains the jev + typesafe_key interaction and hints that seller supplies terms, but api_key, chain_id, and the required task parameter get no meaning at all.

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+resource: auto-suggest the inputs of a hire from LIVE data, enumerating what is suggested (skills, budget, terms). However, it does not distinguish this tool from close siblings such as taifoon_hire_assemble or taifoon_hire_pad, which an agent would plausibly confuse it with.

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?

It describes where the suggested data comes from but gives no when-to-use condition, no prerequisite, and no mention of alternative tools (hire_assemble, match, pool_quote) that also serve hiring setup. The only conditional guidance is the jev/typesafe_key pairing, which is about a sub-feature rather than tool selection.

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