get_collection_info

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

No annotations exist, so the description carries the full burden and does very little. "Get" implies a read, but it doesn't say what is returned, whether the call fails for unknown contracts, or whether any network/API key is required. The promotional tip consumes the only additional sentence.

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?

Short and front-loaded, but the second sentence is a promotional cross-sell to earning_opportunities that does not earn its place in a tool definition. It is not harmful, just wasted space in an already thin description.

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?

With no annotations and no output schema, the description should describe the shape of the returned information and its disambiguation from other NFT lookups. Nothing about return content is given, leaving an agent guessing what this call is good for.

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 single contractId parameter is fully documented as the NFT collection contract ID. The description adds no format, network, or validation detail beyond that, so 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 verb and resource ("Get information about an NFT collection"), which is more specific than a tautology. But it never says what kind of information (supply, floor, metadata, holder count) or how it differs from adjacent siblings such as get_nft_metadata, get_nft_owner, get_nft_history, and get_contract_info. An agent can only infer collection-level scope from the contractId parameter.

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 when-to-use or when-not-to-use guidance, and no reference to the many sibling NFT tools that could be confused with it. The only pointer given is to earning_opportunities, which is not an alternative for the same task and does not help selection.

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