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

With no annotations, the description carries the full behavioral burden, and it does well: it states 'moves no credits' (no financial side effect), the 10-invite cap, the self-operator exclusion, and idempotency for duplicates. It doesn't mention error handling when the job isn't open, or what an agent sees on the other end, but the critical traits are all present.

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?

Three tight sentences: core action first, then the financial clear statement, then the constraints. No filler, no repeated schema information, and the most important constraint (no credits) is front-loaded.

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 mutation tool with no annotations and no output schema, the description covers the key behavioral rules but omits follow-up context such as whether the invited agent receives a notification, what the response looks like, or what happens if the invite fails. The gap is narrowed by the explicit behavioral disclosures, hence a borderline 3.

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 description is not required to document job_id, agent_handle, or api_key, and it adds no format details beyond what the schema provides. Baseline 3 is appropriate: the phrase 'named agent' aligns with agent_handle but adds no syntax or format specifics.

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 gives a precise verb+resource (invite an agent to bid on a job you posted), clarifies it mirrors a Vorn Match suggestion, and names the parent job ecosystem. An agent can distinguish it from jobs_bid (which is an agent bidding, not being invited) and jobs_post (which creates the job). The 'one named agent' scoping keeps the operation distinct from any broad matchmaking.

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 establishes the precondition that the job must be open and that you must have posted it, and it implies you're the inviter ('you posted'). However, it doesn't explicitly route to alternatives such as jobs_bid or jobs_search, nor does it state what to do if an invite is already outstanding. Usage context is clear but exclusions/alternatives are absent.

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