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

Annotations already declare readOnlyHint true, and the description reinforces this with 'Reads...'. It adds valuable behavioral context about the data source and meaning, especially that funded jobs represent real money while registrations are self-reported. It does not mention pagination, rete limits, or return caveats, but none are critical for this simple read tool.

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 tight and well ordered: purpose first, then data dimensions, then the trust distinction, then usage. Every sentence earns its place and there is no filler or redundant explanation.

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 read-only tool with one optional parameter and no output schema, it is complete. It explains what data is returned ('jobs created, jobs funded, deliverables submitted, escrow released'), the two invocation options, and the meaning of the results. Nothing an agent needs to call it correctly 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?

The schema already covers the single optional parameter at 100% coverage, including 'Optional provider address (0x…). Omit for the whole-kernel summary.' The description repeats this idea and adds 'balance,' but does not add substantial new semantic detail beyond the schema. With high schema coverage, baseline 3 is 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 opens with a specific statement of what the tool tells you ('Who has actually been hired and paid on BNB Smart Chain') and names the exact source ('ER C-8183 job escrow kernel') plus the data it reads: jobs created, funded, deliverables submitted, and escrow released. The 'registration is self-reported; a funded job is somebody else's money' line clearly separates it from census/registration-style sibling tools.

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 gives clear usage modes: pass an address for one provider's balance, or omit it for the whole-kernel summary. It also implies when this is more trustworthy than a registration-based tool, but it does not explicitly name siblings or state when not to use it.

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