List scanned projects

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

No annotations are provided, so the description must disclose behavioral traits. It only describes the action as listing projects, which implies a read-only operation, but does not mention whether authentication is needed, side effects, or dependencies on daedalus init having been run. The brevity leaves significant behavioral ambiguity.

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?

The description is a single sentence, which is concise, but it omits necessary details about parameter, behavior, and output. Conciseness is positive, but under-specification harms usability.

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?

Given the lack of annotations, no output schema, and 0% schema description coverage, the description is severely incomplete. It does not explain return values, parameter usage, prerequisites, or error conditions. The tool's definition is inadequate for an agent to use correctly.

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 input schema has one parameter 'workspacePath' with 0% description coverage. The description does not explain what the parameter does, despite the description mentioning 'el workspace actual'. The parameter's meaning, format, and requirement are entirely unclear.

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 clearly states the tool lists projects detected by daedalus init. The verb 'Lista' and resource 'proyectos detectados' are specific. It distinguishes from sibling tools like daedalus_listGroups (lists groups) and daedalus_run (runs projects).

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 specifies the context 'en el workspace actual', implying it operates on the current workspace. However, it does not explicitly state when not to use it or mention alternatives like daedalus_listGroups. Usage is clear but lacks exclusion guidance.

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