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 key traits: 'no on-chain calls required' (performance/behavior), 'Results are static configuration — not subject to caching or rate limits' (data freshness and rate limit behavior), and 'Returns a structured map of pair identifiers to pool metadata' (output format). This covers safety, performance, and output structure adequately.

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 front-loaded with the core purpose, followed by usage guidelines and behavioral details. Every sentence adds value: the first defines the tool, the second explains output and usage, the third clarifies parameters and behavior. There is no redundant or wasted text.

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's complexity (0 parameters, no output schema, no annotations), the description is complete. It explains what the tool does, when to use it, behavioral aspects like no on-chain calls and static data, and output format. This provides sufficient context for an agent to invoke it correctly without structured 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?

The input schema has 0 parameters with 100% coverage, so the baseline is 4. The description reinforces this by stating 'No parameters required,' which adds clarity beyond the empty schema, ensuring the agent understands no inputs are needed.

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 explicitly states the tool's purpose: 'List all supported trading pairs with their pool addresses, fee tiers, token symbols, and decimal precision on Base mainnet.' It specifies the verb ('List'), resource ('trading pairs'), and scope ('Base mainnet'), and distinguishes from siblings by mentioning it's used before calling get_dex_price or get_pool_liquidity.

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: 'Use this tool before calling get_dex_price or get_pool_liquidity to discover available pairs and understand token ordering.' It also mentions alternatives implicitly by naming specific sibling tools, giving clear context for usage.

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