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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds real behavioral value by disclosing the default filtermode and the exact fields free-text search spans, but says nothing about pagination limits, result ordering, or response shape.

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 compact sentences, front-loaded with the resource definition followed by the two facts that affect invocation (search scope, filtermode default). The trailing 'Current RMS: GET /projects' endpoint note is mild filler but not disruptive.

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?

The tool has 7 optional params including a nested free-form filters object and no output schema, so the description could say more about pagination and what a project record contains. The schema carries most of the load, leaving the description adequate but not complete for a list tool with no declared return shape.

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%, so the baseline is 3. The description contributes the default value for filtermode (active) and restates search scope, but adds little beyond the schema, which already documents page, sort, filters, view_id and per_page in detail.

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 (list projects) and adds a definition of what a project is ('groups of related opportunities for one customer or event'), which helps an agent distinguish it from the many list_* siblings. It stops short of explicitly naming which sibling to use instead, but the resource nouns are distinct enough that confusion is unlikely.

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?

Gives useful operational context (search covers name/customer/tags; filtermode defaults to active), which implies when to reach for this tool. However, there is no explicit when-to-use vs alternatives guidance and no stated exclusions, so usage is only implied.

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