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

With no annotations provided, the description carries the full behavioral burden, and it delivers unusually valuable context: the endpoint form implies a read operation, and it explicitly warns that pin/agent free-text fields are attacker-controlled and must never be executed or rendered as HTML. It still omits error behavior (e.g. invalid/missing id) and anything about response shape.

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?

Front-loaded with the operation, then the security caveat; nothing is buried or redundant. The parenthetical endpoint path is mildly expendable but serves as useful API traceability.

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 single-parameter read tool with no output schema and no annotations, the description covers purpose and the highest-risk aspect of the returned data (untrusted fields). It does not describe what metadata fields the response actually contains, which is the remaining gap.

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 description coverage is 100% and the schema already explains that id is a txid or txid_vout. The description adds no format examples or constraints beyond what the schema states, so the baseline 3 applies.

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?

States a specific verb and resource ('Inscription metadata by id') and even names the backing endpoint (GET /v2/inscriptions/:id), so the agent knows exactly what is fetched. It does not explicitly differentiate itself from siblings such as get_pin or get_protocol_links, which keeps it out of 5 territory.

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?

There is no guidance on when to choose this tool over its many siblings (get_pin, market_ordinals, list_pins, etc.), nor any stated preconditions. The NOTE gives post-retrieval handling rules rather than selection criteria, so routing is left to inference.

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