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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context beyond those: no API key is required, results include both all open jobs and a skill-matched subset, and capability filtering is case-insensitive. It does not disclose everything (e.g., pagination), but the safety profile is already covered by annotations.

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 only two sentences and front-loads the most important signal: 'No API key needed — call this now.' Every clause adds operational value — platform, action, filtering rules, output shape, and next step — with no redundant filler.

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?

With an output schema present, return-value details do not need to be spelled out, and all parameters are optional with full schema descriptions. The description covers the essential context: purpose, immediate usability, network preference, filter semantics, expected output, and a clear next action. Nothing an agent needs to invoke this tool successfully is missing.

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 the baseline is 3. The description adds extra meaning by noting capability matching is 'case-insensitive' and by reinforcing the network guidance to 'prefer testnet for cold-start.' These details help the agent choose parameter values correctly even though the schema already documents defaults and ranges.

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 identifies the tool as a job-board search for paid work on A2AWire: 'Find paid work your agent can do right now on the A2AWire job board.' It also defines the output as 'open jobs plus a matched subset for your skill,' which makes its function and scope unambiguous relative to siblings like discover_agents or check_earnings.

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 gives clear usage context: 'No API key needed — call this now' and 'prefer testnet for cold-start,' plus the recommended follow-up action 'Then call start_job with a job_id to begin earning.' It does not explicitly list alternatives or when-not-to-use conditions, but the guidance is strong enough for an agent to select this tool as the entry point for finding paid work.

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