Ordiscan: getRecentStamps

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds value by detailing the response content (asset name, image preview, etc.) but doesn't elaborate on potential rate limits or additional behavior beyond what annotations imply.

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 two sentences, each serving a purpose: stating the action and outcome, and recommending use cases. No redundant or extraneous information. Front-loaded with key details.

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 simple read-only tool with one optional parameter and no output schema, the description fully covers what the tool does, what it returns, and when to use it. No gaps are evident given the tool's complexity.

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 single parameter (limit) is fully described in the schema with constraints and default. Schema description coverage is 100%, so the baseline is 3. The description does not add further parameter-specific guidance but references output fields, which is helpful context.

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 it retrieves the most recently issued Bitcoin Stamps in newest-first order, specifying returned fields (asset name, image preview, creator, timestamp) and use cases ('activity feeds and what's new surfaces'). It effectively distinguishes itself from sibling tools like getStamp (individual) and getStampsByAddress (by address).

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 explicitly recommends using this tool for activity feeds and discovery. While it doesn't state when not to use it, the context from sibling tools implies alternatives, and the guideline is clear enough for decision-making.

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