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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real behavioral context beyond that: only published projects are returned, empty queries fall back to browsing, and results are deterministically ordered by name and slug. It stops short of mentioning pagination behavior or result shape, but it clearly earns credit over the annotations.

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?

Two short sentences with no filler, and the core purpose is front-loaded ahead of the edge-case behavior. Every clause carries information.

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?

There is no output schema, so the description's note about ordering partly compensates, and the empty-query rule is helpful. But for a 4-parameter search tool with zero schema documentation, the absence of any guidance on limit/offset paging and on the category filter leaves real gaps.

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% across 4 parameters, so the description carries the burden. It clarifies the query parameter's semantics (matches name, description, or tag), which is valuable, but limit, offset, and especially category are entirely undocumented in both schema and description — and the unexplained category filter is notable given list_project_categories is a sibling.

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?

Specific verb (search) plus resource (published HoodL2 projects) and the fields matched (name, description, tag). The scope word 'published' is a meaningful qualifier, and the 'empty query browses the directory' sentence further pins down behavior. It doesn't name its siblings, but 'search'/'get'/'list categories' are readily distinguishable.

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 gives one concrete usage rule — an empty query browses rather than searches — which is genuinely useful for choosing how to call it. However, it never says when to use this instead of get_project (which presumably needs a known slug/name) or list_project_categories, even though category is one of its own parameters.

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