nft_floor

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals that the tool returns floor price in SOL and lamports, average 24h price, and total volume, which is helpful. However, it does not mention potential error states, rate limits, authentication needs, or whether the data is real-time, leaving gaps in behavioral transparency.

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 concise, consisting of two clear sentences. The first states the primary action and scope, and the second lists the return fields. There is no extraneous information, and the key details are front-loaded.

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 description is adequate for a simple data-retrieval tool with one parameter. It explains what is returned, but it lacks context about when to use this tool over siblings, any prerequisites, or edge cases. Given the tool's simplicity, the information is sufficient but not comprehensive.

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 covers the single parameter 'symbol' with a description that includes examples. The tool description does not add further semantic meaning beyond the schema. Since schema description coverage is 100%, the baseline score is 3, and no additional param context is provided.

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 specifies the tool's function: getting floor price and listing count for a Magic Eden Solana NFT collection. It uses a specific verb ('Get') and resource ('NFT collection'), and the output details (floor price in SOL/lamports, average 24h price, total volume) distinguish it from sibling tools like nft_stats or nft_listings.

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 implies usage when a user needs floor price and listing count data, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., nft_listings for individual listings, nft_stats for broader stats). No exclusions or caveats are mentioned.

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