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

With no annotations provided, the description carries the disclosure burden. It reveals that every ERC-8004 registration is probed on-chain, only alive and hireable agents are returned, and the output includes probe age, latency, and permanent evidence. It also mentions the required auth/payment condition. It does not mention rate limits or explicit read-only behavior, but given the query-like nature it is reasonably transparent.

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 not front-loaded. Payment and authentication details dominate the first sentence, pushing the actual purpose to the second. The text is dense and includes repeated concepts such as 'alive and hireable' and 'on-chain/on BNB Smart Chain', making it harder to parse than necessary.

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?

Given a single optional parameter and no explicit output schema, the description supplies enough to call the tool: it names the returned fields, the verification process, the filter options, and the auth/payment requirements. The main gaps are lack of pagination, error behavior, and rate limit details, but these are secondary for a simple list tool.

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 0%, so the description should compensate. It only repeats the enum values without explaining what 'hireable' vs 'alive' means, whether the status field is a filter, or what happens if it is omitted. The phrase 'Optional status hireable or alive' mirrors the schema rather than adding useful semantics.

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 identifies the resource: verified live agents on BNB Chain, and explicitly says the tool lists agents that are actually running and hireable with endpoint, skills, latency, and evidence. It does not use an explicit verb like 'list' or 'get', and does not distinguish itself from sibling tools, so it falls short of a 5.

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?

There is an implied use case: when you need the current map of verified running/hireable agents on BNB Smart Chain, and an optional status filter of 'hireable' or 'alive'. However, it never explicitly explains when to choose this tool over alternatives or when not to use it, so we have inferred usage, not clear guidance.

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