Ordiscan: getStamp

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds no behavioral context beyond 'Get', which is consistent with readOnly. However, it doesn't disclose what information is returned or any limitations (e.g., rate limits, data freshness). The annotations carry the burden, so this is minimally adequate.

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 too short (one sentence) and lacks necessary detail. It is under-specified, not concise. Every sentence should earn its place, but this sentence provides minimal 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?

Given the complexity of sibling tools and the lack of output schema, the description should explain what data is returned (e.g., stamp details, metadata). It does not, leaving the agent uninformed about the tool's output or behavior beyond the required parameter.

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 coverage is 100% with a single parameter 'stampId' described as 'The id of the stamp'. The description adds no additional meaning beyond the schema. According to the rubric, with high coverage, baseline is 3.

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 'Get the bitcoin stamps' is vague and ambiguous. It does not specify whether it retrieves a single stamp or multiple, nor does it clarify the type of stamps (e.g., SRC-20). Given the required 'stampId', it likely fetches one stamp, but the plural form is confusing. It fails to distinguish from sibling tools like 'getStampsByAddress' or 'searchStamps'.

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 guidance on when to use this tool over alternatives. With many stamp-related sibling tools (e.g., getRecentStamps, searchStamps), the description provides no context for selection or exclusions.

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