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

Since no annotations are provided, the description fully handles transparency. It states the tool returns 'no owner identity string and no payment amounts — those are paid', which is a critical behavioral disclosure. It also notes the return of an 'error' field if the agent is not indexed. This is honest and informative.

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 exceptionally concise with zero wasted words. It front-loads the purpose in the first sentence, then lists parameters, then described returns succinctly. Each sentence adds unique value—purpose, params, returns, usage hint. The structure is ideal for an agent to quickly parse.

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 the tool has an output schema only described inline (no formal output schema), the description covers all needed behavioral and return details. It lists all returned fields, flags what is not returned, and notes error behavior. For a 2-parameter tool with clear inputs, this is complete. Minor omission: no explanation of how 'reachability' or 'well-known presence' are determined, but likely domain-knowledge.

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 description provides semantic detail for both parameters: 'chain: one of "base", "ethereum"' and 'agent_id: the numeric ERC-8004 agent id'. This adds meaning beyond the raw schema, which only lists types and titles. With 0% schema coverage, the description fully compensates. The only minor gap is that it doesn't clarify the allowed formats for chain values explicitly (though implied).

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 tool returns 'counts-only signals for one ERC-8004 agent', listing specific fields like reachability, TLS validity, and agent status. The verb 'get' paired with 'agent_summary' makes the purpose obvious. It distinguishes itself from siblings like get_coverage_stats and get_leaderboards by focusing specifically on a single agent's summary.

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 ends with 'Use this to vet a counterparty agent before transacting', which implies a specific use case. However, it does not explicitly state when not to use this tool or provide alternatives among siblings. The context suggests it's for pre-transaction vetting but lacks explicit exclusions or comparisons.

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