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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real value beyond them: this is a dated snapshot rather than a live call, and measured_at carries the freshness timestamp — an agent that needs live data would otherwise be misled.

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?

Front-loaded with the core question, then scope, then the parameter behavior, then the staleness caveat. Every sentence carries distinct information; nothing is redundant padding.

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 no output schema, the description compensates by enumerating what gets counted (jobs created, funded, deliverables submitted, escrow released) and flagging the snapshot/measured_at caveat. It is nearly complete; the only gap is any hint at the shape or granularity of the returned per-provider record.

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% and the sole parameter is already documented as an optional provider address with omit-for-summary semantics. The description restates that same behavior ('pass an address ... or nothing for the whole kernel') without adding format, validation, or edge-case detail, so the baseline 3 applies.

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?

Names the exact resource (ERC-8183 job escrow kernel on BNB Smart Chain) and the specific signal it returns (hired and paid providers), which cleanly separates it from self-reported registration data and from siblings like bnb_agent_census or find_agents_on_bnb_chain.

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?

Gives concrete call conditions: pass an address for one provider's balance, omit it for the whole kernel. It also contrasts 'a registration is self-reported' against 'a funded job is somebody else's money', implicitly telling the agent when this tool beats a census tool, though it never names the sibling outright.

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