nft_collection_info

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

No annotations are present, so the description carries full burden. It only states 'where exposed', implying potential null returns if the contract lacks these functions, but does not clarify error behavior, permission requirements, or side effects. This is insufficient for a robust understanding.

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 a single sentence that quickly conveys the tool's purpose. It is front-loaded and free of fluff, though 'where exposed' could be more precise. Overall, efficient but minor room for improvement.

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 lack of output schema and low parameter coverage, the description should provide more context about return structure, error handling, or supported chains. Without these, the agent may struggle to interpret the output or handle edge cases.

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?

With 0% schema description coverage, the description must compensate, but it adds no parameter-level details. The sole parameter 'contract' is not explained (e.g., expected format, address requirement). The agent must infer from name alone, which is ambiguous.

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 the tool returns ERC-721 collection name, symbol, and total supply. It specifies the standard and resource type, making the purpose easily understandable. However, it does not differentiate from sibling tools like nft_owner or nft_token_uri, which fetch different aspects of NFTs.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention prerequisites or limitations. The agent has no context for decision-making beyond the basic purpose.

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