List configured local projects

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

The description reveals that the tool returns not just a list but also details like keys, roots, stacks, and existence status. This adds value beyond the `readOnlyHint` annotation, which only indicates safe read 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?

A single, front-loaded sentence efficiently conveys purpose and output details 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 parameterless listing tool, the description sufficiently explains what it returns. While there is no output schema, the description gives enough context for the agent to interpret results.

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?

With zero parameters, the input schema is fully covered (100%). The description compensates by specifying the output fields, providing meaning beyond the empty 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?

The description explicitly states the tool's purpose: to discover project keys, roots, stacks, and root existence. The title 'List configured local projects' reinforces a clear verb-resource pairing. It distinguishes itself from sibling tools like `get_project_info` by offering a broader overview.

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?

The description guides the agent to 'Use this first', providing clear context for when to invoke it as an initial discovery step. It does not explicitly exclude cases or list alternatives, but the primary usage is well-defined.

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