Ordiscan: getInscriptionInfo

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the description need not repeat safety traits. However, it does not add behavioral details like return format (e.g., metadata fields) or response characteristics beyond the basic operation.

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?

A single, front-loaded sentence with no extraneous words. Every phrase earns its place, making it optimally concise for a simple tool.

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 no output schema and one parameter, the description is minimally adequate. However, it lacks context on what 'inscription info' contains (e.g., metadata, owner, content type) and does not address sibling tool differentiation, leaving gaps for an agent.

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 description mentions 'for a given inscription id', which adds minimal meaning beyond the schema's parameter name 'inscriptionId'. With 0% schema description coverage, it does not compensate with format, examples, or constraints, but the parameter name is self-explanatory.

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 inscription info for a given inscription id' clearly states the action and resource. However, with many sibling tools like getInscriptionActivity, getInscriptionTraits, it does not differentiate what 'inscription info' specifically entails, reducing distinguishability.

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 versus alternatives (e.g., getInscriptionActivity) or when not to use it. The description lacks context for deciding between similar inscription-related tools.

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