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

The description adds valuable behavioral context beyond the readOnlyHint annotation: it explains that the tool combines floor price, competing bids, and set composition, and discloses a rate limit of 1 per 1 minute. It does not mention return format or side effects, but for a read-only recommendation tool, the added context is sufficient.

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 and front-loaded with the main purpose. However, the sentence about `composition`/`absentTraits` is cryptic and adds confusion without clearly earning its place. Overall, it is still compact and structured, but the misleading term reduces clarity.

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 output schema, the description should explain what the response contains; it only implies a bid price range but doesn't specify the structure. The parameter interactions and the odd `absentTraits` reference leave gaps. Given the tool's moderate complexity, the description is not fully complete, though it covers the core purpose and rate limit.

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 description references `composition` and `absentTraits`, neither of which exist in the input schema (which has `includedTraits` and `excludedTraits`). This is misleading because an agent might try to pass `absentTraits` as a parameter, but the schema has additionalProperties: false, so it would be rejected. The description does not clarify the actual parameters beyond what the schema already states, and the erroneous instruction detracts from 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 states 'Analyze market data and recommend a bid price range for a CryptoPunk trait selection,' giving a specific verb ('recommend') and resource (bid price range). It distinguishes itself from sibling tools like get_floor_price or get_bids_for_punk by combining multiple data sources into actionable guidance.

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 provides context for when to use the tool (for a CryptoPunk trait selection) and includes a rate limit warning, but it does not explicitly state when to prefer this over siblings or exclude situations. The note about 'use `absentTraits` for a full exclusion list' is potentially confusing because `absentTraits` is not a valid input parameter in the schema, so it misleads rather than guides.

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