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

Annotations already mark this as read-only, open-world, idempotent, and non-destructive. The description adds valuable context beyond those annotations: no API key is required, and it explains that the tool returns both open jobs and a matched subset for the agent's skill.

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 short, front-loaded with the most important call-to-action, and each sentence adds relevant information. The emoji and urgency phrasing are slightly informal but do not reduce clarity.

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 simple 3-parameter, all-optional tool with a rich output schema, the description covers what the tool does, how to filter, what to expect in return, and how to proceed afterward. The only minor gap is that start_job is not among the listed sibling tools, but that does not undermine this tool's own completeness.

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 parameters are already documented with defaults and meanings. The description adds only minor extra guidance, such as 'case-insensitive' capability matching and the cold-start preference for testnet, which is also partially present in the schema.

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 clear verb and resource: 'Find paid work your agent can do right now on the A2AWire job board.' It also names the key filters (capability, network), which distinguishes it from sibling tools focused on earnings, sessions, or onboarding.

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 explicit usage context: 'call this now', 'No API key needed', and 'prefer testnet for cold-start'. It also gives a clear next step by saying to call start_job with a job_id, though it does not explicitly discuss alternatives or when not to use this tool.

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