social_get_nft_collections

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 only says 'Get social metrics' and reveals nothing about default sorting, limits, output format, or any non-obvious behaviors. This is a minimal, implicit read operation with no behavioral detail.

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 one concise sentence with no filler or redundant wording, and the key action and object are front-loaded. It loses some points for not including any supplementary structure, but it is efficient for the size of the tool.

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?

The tool has no output schema, so the description should explain what 'social metrics' actually returns (e.g., collection names, metric values, units), but it does not. It also fails to clarify sorting options or how 'limit' affects results, making the description incomplete for a useful agent.

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 covers 100% of parameters with descriptions for 'sort' (enum with options) and 'limit' (number of collections). The description adds no extra parameter meaning, so the schema's rich coverage makes the baseline 3 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 clearly states the tool gets social metrics for NFT collections, which is a specific verb+resource pair. However, it does not differentiate itself from the sibling tool 'social_get_nft_collection' (singular), so the plural scope is ambiguous.

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 the singular 'social_get_nft_collection' or other social metrics tools. There is no mention of trade-offs, prerequisites, or suggested contexts, so the agent has no basis for tool selection.

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