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 behaviors: 'No on-chain calls — instant response' (performance characteristic), 'Free tier — no payment in standalone mode; $0.001 USDC via x402 on the resource server' (cost/payment model), and 'Returns up to 5 matching entries ranked by relevance' (output limitation and ranking). However, it doesn't specify error handling or rate limits.

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 appropriately sized and front-loaded with the core purpose. Every sentence adds value: the first states the purpose, the second details scope and examples, the third describes output format and limitations, the fourth covers behavioral aspects, and the fifth provides usage guidance. Minor redundancy exists in listing the 15 topics.

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 moderate complexity (search function with cost considerations), no annotations, and no output schema, the description does well by explaining the knowledge base scope, output format ('each with id, title, tags, and full content'), behavioral traits, and usage context. However, without an output schema, it could benefit from more detail about the response structure.

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%, providing a comprehensive description of the single 'query' parameter. The description adds minimal value beyond the schema by mentioning 'keyword matching against 15 entries' and listing example topics, but doesn't provide additional parameter semantics beyond what's already documented in the schema.

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's purpose: 'Search a curated DeFi knowledge base covering Base chain DeFi protocols and concepts.' It specifies the verb ('search'), resource ('curated DeFi knowledge base'), and scope ('Base chain DeFi protocols and concepts'), distinguishing it from sibling tools like get_dex_price or compute_agent_score which perform different functions.

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 before calling get_dex_price or compute_agent_score to understand the underlying concepts.' It also mentions alternatives implicitly by listing sibling tools and specifying this is for knowledge retrieval, not on-chain operations or calculations.

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