summarizeNFTAttributes

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

With no annotations provided, the description must fully disclose behavioral traits. It only states that a 'summary' is returned, without specifying what the summary includes (e.g., counts, percentages, all traits or top ones), whether it is computationally expensive, or if caching applies. This lack of detail leaves uncertainty about the tool's behavior.

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, which is concise but somewhat vague. It could benefit from additional brevity while adding more detail, or being restructured to front-load critical information. Currently, it is adequate but not exemplary.

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?

There is no output schema, so the description should explain what the summary looks like or the structure of the return value. It fails to do so, leaving the agent uninformed about the result format. Given the tool's moderate complexity (2 parameters, no nesting), the description is incomplete.

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 input schema already provides full descriptions for both parameters (network and contractAddress) with 100% coverage. The description does not add any additional meaning or context beyond the schema, so 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 clearly states the action ('get a summary') and the resource ('NFT collection'). It specifies the focus on 'trait/attribute distribution', which is specific. However, it does not differentiate from the sibling tool 'computeRarity', which may have overlapping functionality, preventing a score of 5.

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 computeRarity or other NFT-related tools. There are no examples or contextual hints about prerequisites or ideal scenarios, leaving the agent without decision support.

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