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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. Beyond them the description adds real behavior: only published projects are returned, results are ordered by name and slug, and an empty query falls back to directory browsing. It does not describe pagination behavior across limit/offset, which is the main remaining gap.

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?

Three short sentences, front-loaded with the verb and resource, and every sentence carries information (scope, fallback behavior, ordering). No filler or repeated annotation content; the ordering sentence is the only borderline detail.

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 is the only source for return shape, and it delivers ordering and the published-only filter but nothing about pagination totals or result fields. With four undocumented parameters and a list-returning tool, the definition is adequate but leaves meaningful 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 four parameters, so the description must carry the meaning. It only illuminates 'query' (searched fields plus empty-string default), leaving limit, offset, and category entirely unexplained. A caller has no idea that category filters by taxonomy or that limit/offset drive pagination.

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+resource ('Search published PM Wisdom projects') and narrows scope to name, description, or tag matches. It also explains the degenerate case (empty query browses the directory). It never names its siblings, so the agent must infer how it differs from get_project on its own.

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 'empty query browses the directory' clause gives one concrete usage condition, so the agent knows the tool doubles as a browse endpoint. However, there is no guidance on when to prefer get_project for a known project or list_project_categories for taxonomy, and no stated prerequisites or limits on result volume.

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