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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the bar is lower; the description reinforces this by stating the call neither creates nor changes a design, and notes the result is an embedded list with icons. It adds no auth or scale/limit details, but the key behavioral risk (accidental mutation) is explicitly cleared.

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 sentences, front-loaded with what is listed, followed by the one behavioral fact an agent would otherwise guess at (no design side effects). No filler or restated title text.

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?

With an output schema present, return values need not be spelled out, and annotations cover the safety profile; the description supplies the remaining useful context (scoping to the authenticated user, downstream use of the ID). Only a brief pointer to sibling tools like get_project would make it fully complete.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema also has 100% coverage, so no compensation is required.

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 with scope: 'Lists the authenticated user's existing AppLaunchFlow projects' and adds the return shape (embedded project list with icons). It does not explicitly differentiate from get_project (singular fetch) or create_project/delete_project, leaving that to the naming convention.

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?

'Choosing a project supplies its ID to the chat without creating or changing a design' gives clear context for why an agent would call this and what to do with the result. It stops short of naming alternatives (e.g., get_project for details on one project) or stating when not to use it.

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