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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine domain context about the type/kind overlap (the four kinds share type='node'), but says nothing about result limits, pagination, or ordering. Adequate given the annotation coverage, but not rich.

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?

One front-loaded sentence with the core verb+fields first, followed by the clarifying parenthetical. Dense but every clause earns its place; the nesting makes it slightly harder to scan than an ideal split into two sentences.

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 read-only search with no output schema and 100% schema coverage, the description covers the main subtlety (kind vs type). The only gaps are return-shape/pagination hints, which are minor for a filtered list tool whose annotations already carry the safety profile.

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 coverage is 100% and both enums are fully documented in the schema, including the legacy type note. The description restates and slightly contextualizes the kind/type semantics rather than adding syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (searches) and resource (blocks/cells) and enumerates the fields searched (name, description, type, kind). An agent can distinguish this from sibling mutators like add_cell/update_cell and from list_entities. It does not explicitly name a sibling alternative, so it stops short of a 5.

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 parenthetical gives a concrete usage example (listing all captable holders or arch services) and explains the kind-vs-type relationship, which implies when this tool is the right choice. However, it never states when NOT to use it or names an alternative such as list_entities or search_people, leaving routing to inference.

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