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

No annotations are provided, so the description must convey behavioral traits. It adds a cost of 0.5 credits, a useful behavioral detail, but lacks information on return structure, sorting, pagination, or error handling. Compared to the absent annotations, the description provides minimal but non-contradictory context.

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 consists of two concise sentences, front-loading the core purpose then adding cost. No unnecessary words or repetition, making it easy to parse quickly.

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?

Given no output schema and 0% parameter coverage, the description is incomplete. It does not specify result format (e.g., list of block IDs/objects), ordering (by usage or rating?), or pagination. The agent lacks enough context to fully understand the tool's behavior and output.

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?

Schema description coverage is 0%, so the description must compensate. It explains 'domain' and 'category' as optional scoping, and implies 'limit' through 'top blocks', but does not define parameter formats, defaults, or constraints. This partial compensation is insufficient for full understanding.

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 returns 'top blocks by usage/rating' with optional scoping by 'domain/category'. This distinguishes it from sibling tools like 'get_block' (single block) and 'search_blocks' (text search).

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 needing trending blocks, but provides no explicit guidance on when to use this over alternatives (e.g., 'search_blocks' for text queries). No exclusions or context for sibling tools are mentioned.

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