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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds context the annotations don't: archived projects are excluded by default, and the call requires a Cotlet API key with access to this app. It does not mention pagination or result limits.

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?

Front-loads the resource and its fields, then the filtering behavior, then the downstream integration and auth note, with no filler. The first sentence is slightly comma-heavy but still legible.

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?

No output schema exists, but the description compensates by naming the fields projects carry, and it covers the archive default and the API-key prerequisite. For a two-param read tool this is essentially complete, missing only pagination/limit expectations.

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 both parameters are already documented in the schema. The description's 'optionally for one client' and 'unless you ask' only paraphrase client_id and include_archived without adding format or syntax detail, so the baseline of 3 is appropriate.

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 ('Lists') and resource ('projects'), and enumerates the fields returned (client, status, Project Leader, dates). It distinguishes itself from write siblings like create_project by naming the related downstream tools add_task and list_tasks, though it does not explicitly contrast with other list tools in the family.

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 clear context for the optional client filter ('optionally for one client') and the default archive behavior ('Archived projects are left out unless you ask'), plus a workflow pointer that project_id feeds add_task and list_tasks. It lacks an explicit when-not or named alternative, so it stops short of a 5.

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