nft_get_floor_price

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

There are no annotations, so the description must carry the full burden of behavioral disclosure. It does not state that this is a read-only operation, nor does it mention rate limits, caching, possible errors, or any side effects. The only added context is the VeChainStats data source, which is minimal.

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 with a useful parenthetical source note. It is front-loaded with the key verb and resource, contains no filler, and every word contributes value.

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 a single-parameter read tool, the description is reasonably complete: it names the return scope (floor price and market data), the required identifier, and the data source. However, it could be stronger with a note on the output shape or usage constraints, especially since no output schema is provided.

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 fully documents collectionId with type and description ('NFT collection ID or contract address'). The description adds no new meaning beyond reaffirming that the tool operates on an NFT collection, so it does not improve on the 100% schema coverage.

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 identifies the action (get), the resource (floor price and market data for an NFT collection), and distinguishes it from siblings like nft_get_collection_info by focusing on pricing data. The verb 'Get' plus the specific resource makes the purpose immediately obvious.

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 about when to choose this tool over alternatives such as nft_get_collection_info, nft_get_metadata, or vechainstats_get_nft_info. The only implied usage context comes from the tool name and the phrase 'NFT collection,' but no explicit when-to-use or when-not-to-use information is given.

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