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

Annotations already cover readOnly, idempotent, and non-destructive, so the bar is lower; the description still adds real context by noting the results are scoped to what 'this connection can see' (permission boundary) and that counts come back with status. It does not mention pagination or result-size limits, keeping it out of 5 territory.

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 short sentences, zero filler. The what (list projects + status counts) is front-loaded, with the usage hint following immediately.

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 no-required-param read-only listing tool with no output schema, the description covers purpose, scope, and the discovery role it plays in the toolset. The only real gap is the undocumented include_archived flag and any hint of result volume.

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 only 50%: 'query' is documented as a partial-name filter, but 'include_archived' carries no description in either the schema or the tool description. The description adds no parameter guidance at all, so it neither compensates for the coverage gap nor improves on what the schema provides.

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 and resource ('List the Chief projects') with an added scope qualifier ('this connection can see') and an output hint ('with status counts'). This clearly distinguishes it from siblings like list_milestones or get_milestone without needing to open the 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?

Explicitly names the workflow position: 'Use it to resolve a project name before calling other Chief tools.' That is a clear when-to-use statement. It lacks any when-not-to-use or named alternative, so it falls 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.