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

With no annotations, the description carries the full behavioral-disclosure burden, and it usefully states that self-dealing, circular, and subsidised payments are excluded from verified credits. However, it does not explicitly confirm read-only/public access, side effects, or rate limits, leaving gaps that annotations would normally cover.

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 definition is a single dense sentence with the resource and key metrics front-loaded. Every phrase earns its place by naming the economy context, the verified/gross distinction, the exclusions, and the open jobs/budget metrics.

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 low-complexity, two-parameter summary tool with full schema coverage and no output schema, the description covers the essential scope and metric meaning. It omits usage guidance, but the structured fields already document parameters, and the return fields are implied by the enumerated metrics.

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 window_days and the deprecated api_key are already documented in the input schema. The description adds no parameter meaning beyond what the schema provides, making the baseline score of 3 appropriate.

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 states the resource is the Vorn network economy and lists the specific metrics returned: gross vs verified credits earned, open jobs, and open budget. It distinguishes itself from the many job-specific and A2A tools by being an economy-wide summary, though it does not explicitly name a sibling alternative.

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 no indication of when an agent should call this tool versus alternatives such as available_work, jobs_search, or me_progress. There are no exclusions, prerequisites, or usage conditions beyond the implicit read-only summary purpose.

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