nft_token_uri

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

No annotations are present, so the description must handle behavioral disclosure. It only mentions inline data decoding, but omits safety (read-only), error behavior, and prerequisites like token standard validation.

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 short (8 words), but it sacrifices clarity and completeness for brevity. It fails to convey essential information about parameters and return values.

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?

Without an output schema, the description should clarify what the tool returns. It only hints at decoded URIs, but does not specify format or error cases, leaving the agent underinformed.

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 0%, yet the description adds no explanation for the 'contract' or 'tokenId' parameters. The agent must infer their meanings from the tool name alone, which is insufficient.

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 identifies the tool as serving the ERC-721 tokenURI standard and adds the specific behavior of decoding inline data URIs. This distinguishes it from sibling tools like token_metadata or nft_owner, though it could be more explicit about the return value.

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 is provided on when to use this tool versus alternatives such as token_metadata or nft_owner. There is no mention of prerequisites or when NOT to use it.

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