Ordiscan: searchStamps

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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which suggest a safe, read-only, idempotent operation. However, the description adds no additional behavioral context beyond what annotations imply, such as rate limits, authentication needs, or return format details.

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 extremely concise (one sentence), but it is under-specified and not front-loaded with critical information. It lacks details that would justify its brevity, making it more of a placeholder than an effective summary.

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 (10 parameters, no output schema), the description is completely inadequate. It does not explain what stamps are, how the search differs from other stamp tools, or how to use the various filters (query, creator, collection_id, etc.). This leaves an AI agent with insufficient context to use the tool correctly.

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 10 parameters with 0% description coverage, meaning no parameter descriptions exist. The description does not mention any parameters, leaving the agent to infer their meaning from names alone. With such low coverage, the description should compensate but does not.

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 states 'Search for stamps' which identifies the action and resource, distinguishing it from other stamp-related tools like 'getStamp' and 'getStampsByAddress' that retrieve specific stamps. However, it does not specify what kind of stamps (e.g., Bitcoin stamps), leaving room for ambiguity compared to other search tools on the server.

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?

No usage guidelines are provided. The description does not indicate when to use 'searchStamps' versus alternatives such as 'getRecentStamps', 'searchSRC20Tokens', or other search tools. It fails to give any context on prerequisites or appropriate scenarios.

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