agentshield-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's behavior: read-only operation ('Read-only — no side effects'), cost implications ('Free — no payment required'), return format details ('Returns registration status and available metadata fields; unregistered agents return registered: false with null metadata'), and data source specifics ('ERC-8004 registry on Base mainnet'). It doesn't mention rate limits or error handling, but covers core behavioral aspects well.

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 efficiently structured with zero wasted sentences. It front-loads the core purpose, then provides behavioral details, and concludes with clear usage guidance. Each sentence adds distinct value: identity lookup, behavioral traits, and alternative tool reference.

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 single-parameter read-only tool with no output schema, the description provides excellent context about what the tool does, its behavioral characteristics, and when to use it versus alternatives. The main gap is the lack of output schema documentation, but the description compensates by describing the return format ('Returns registration status and available metadata fields').

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 the schema already fully documents the single 'address' parameter with its format, validation, and example. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 for adequate coverage through structured data alone.

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 specific action ('Look up an agent's on-chain identity'), resource ('ERC-8004 registry on Base mainnet'), and scope ('Reads isRegistered() and...fetch name, endpoint, and registration timestamp'). It distinguishes from sibling tools by explicitly naming 'compute_agent_score' as an alternative for different functionality.

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 provides explicit guidance on when to use this tool ('Look up an agent's on-chain identity') versus alternatives ('Use compute_agent_score to get a full utility score that incorporates ERC-8004 status alongside ETH balance and transaction history'). It clearly defines the tool's scope and when to choose a different tool.

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