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

Annotations already declare the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the description is not burdened with that. It adds useful behavioral context beyond annotations: the exact filter scope (owned + active member), the shape of the returned summaries (name, website, counts of scripts and ideas), and support for free-text search and paging. It does not contradict 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?

The description is three tightly written sentences that front-load the scope, then describe return shape and alternatives, then note search and paging. Every sentence earns its place with no redundancy.

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 list tool with no output schema, the description covers scope, returned fields, alternatives, search, and paging—enough for an agent to call it correctly. A minor gap is that it does not explicitly mention whether a project identifier is returned, which an agent might need to chain into 'get-project'.

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 schema already documents all three parameters in detail. The description mentions free-text search over the project name and paging, which merely restates the schema's own explanations without adding syntax, defaults, or additional meaning.

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?

The description states a specific verb and resource ('List the projects') and immediately clarifies the scope (owned plus active member). It explicitly distinguishes the tool from 'get-project' and 'search', which return detailed content, so an agent can tell this apart without opening any sibling schema.

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?

It names the alternative tools explicitly ('call get-project for one project, or search to find content across all of them') and gives the condition that selects each one. It also states what the tool does not return ('not what is inside them'), providing clear when-to-use and when-not-to-use guidance.

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