nft_get_collection_info

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It simply restates the tool's name ('Get detailed information') and offers no information about side effects, safety (e.g., read-only nature), required permissions, error cases, or return format. This is essentially a tautology and provides zero transparency beyond what the name implies.

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 concise sentence, front-loaded with the action and resource. It has no wasted words. However, it is almost identical to the tool name, so while efficient, it doesn't add much value beyond the name.

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 an info-retrieval tool with no output schema and no annotations, the description is quite sparse. It does not specify what 'detailed information' includes (e.g., name, symbol, total supply, floor price), nor does it clarify the distinction from nft_get_metadata or vechainstats_get_nft_info. The description is minimally adequate for a simple get tool but lacks the depth needed for an agent to confidently choose it among many similar NFT tools.

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 schema already provides 100% coverage of the single parameter, collectionId, with a clear description ('NFT collection ID or contract address'). The description adds no additional meaning or context about the parameter. Given the high schema coverage, a baseline score of 3 is appropriate.

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 detailed information about an NFT collection' clearly states the action (get) and the resource (detailed information about an NFT collection). It distinguishes from sibling tools like nft_get_owned_tokens (tokens owned by a user), nft_get_metadata (metadata for a specific token), and vechainstats_get_nft_info (NFT-level info) by focusing on the collection-level scope.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of scenarios where this tool is preferred over nft_get_all_collections, nft_get_metadata, or vechainstats_get_nft_info, nor any exclusions. The agent is left to infer usage from the name alone.

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