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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real value beyond that: it clarifies that listing is scoped to the authenticated token unless a team is supplied, and exposes the underlying REST routes (with the alternate team path), helping an agent predict behavior.

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 tight sentences with the core purpose front-loaded before the usage hint and endpoint detail. The raw REST paths are slightly redundant for an MCP caller, but they remain short and are placed last.

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 parameterless-required, read-only list tool with a fully described schema and no output schema, the definition is nearly complete: it covers scope, purpose and first-call usage. It only omits any hint about the shape of returned project records/pagination, which is a minor gap given cursor and per_page are already in the schema.

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 page, cursor, per_page and teamId are each documented in the schema, establishing the baseline of 3. The description only restates the team-scoping effect of teamId and adds no format or pagination semantics beyond the schema.

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 projects") plus the scoping variants (authenticated token vs a specific team), which cleanly separates it from the singular northflank_get_project sibling. It does not explicitly distinguish itself from the many other list_* siblings, but the resource name carries that distinction.

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?

"Good first call to discover project ids" gives clear situational guidance for when to reach for this tool, and the team-scoping note tells the agent how to narrow results. It stops short of naming the alternative (northflank_get_project) for retrieving a single project, so no explicit when-not guidance.

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