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

With no annotations provided, the description adds value by clarifying that last_activity_at is label-DB activity, not on-chain time, and explaining coverage_status values. However, it does not disclose other behavioral aspects like idempotency, rate limits, or prerequisite permissions.

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 one sentence followed by a clarifying note, both concise and front-loaded with the main purpose. No redundancy or fluff.

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 an output schema exists (context confirms) and 3 parameters with full schema coverage, the description adds needed output field clarification. It covers the essential behaviors for a filtered list tool, though it omits pagination details beyond the limit parameter.

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 100% (all three parameters have descriptions), so baseline is 3. The description does not add extra meaning to the parameters beyond the schema; it mainly explains output fields. No added value for parameters.

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 it returns named Bitcoin entity rollups with optional filtering by category, and explains key output fields (coverage_status, last_activity_at). This distinguishes it from sibling tools like entity_lookup, entity_categories, and entity_recent_activity.

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 explicit guidance on when to use this tool versus alternatives or when not to use it. The description only states what it does, not the context of use among 45+ sibling tools.

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