resolve_proposal

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

Discloses that it searches across many protocols, returns ranked results with fork info and status, and does not read full specs. No annotations provided, but description sufficiently conveys read-only search behavior.

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?

Well-structured with summary, details, examples, and parameter docs. Slightly lengthy but every sentence contributes value.

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?

Complete for a search tool: covers search scope, return format, parameter guidance, and connection to sibling tools. Output schema exists, so return values need not be detailed.

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?

Despite 0% schema coverage, description thoroughly explains both parameters: query with multiple examples and chain with valid values and usage guidance, adding significant value beyond 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?

Clearly states the tool finds blockchain protocol proposals by keyword, concept, or number. Distinguishes from siblings by mentioning use of returned ID with query_protocol_docs.

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?

Provides explicit examples and guidance on chain filter usage, including when to omit. Lacks explicit when-not-to-use scenarios but adequately covers context.

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