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

Annotations already cover read-only and closed-world safety, and the description adds genuinely new behavioral context: the result set is limited to projects 'Pulse follows' and results are returned most-active-first. It does not discuss pagination or result fields, which is a minor remaining gap given annotation coverage.

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?

A single front-loaded sentence that specifies scope, filter modes, and ordering with no filler. Slight bloat from enumerating the area values already present in the schema enum.

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?

With no output schema, the description should say more about what a result contains (name, area, activity signal) and how `limit` interacts with the 'most active first' ordering. It covers the search behavior adequately but leaves the returned shape implicit.

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?

The schema documents `query` and `limit` but leaves `area` as a bare enum, and the description adds that `query` matches against name, description, or topics — real meaning beyond the schema's 'words to look for'. It also restates the area values, which is redundant with the enum but confirms the OR-combination semantics of query/area/both.

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?

Names a specific verb (search) and resource (projects), plus the fields searched (name, description, topics) and ordering (most active first). It never mentions the sibling `project`, which presumably returns a single project's detail, so the boundary with that sibling must be inferred.

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?

Usage is implied by the 'search the projects Pulse follows' framing and the area filter, so an agent can tell this is a discovery/list tool. However, no explicit when-to-use versus when-not guidance or alternative tools (e.g. `trends`, `recent_updates`, `project`) are named.

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