weeek_list_projects

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

No annotations are provided, so the description carries the full burden. It discloses the return format (array with id, name, parentId, isArchived) and the typical workflow, which adds value. However, it does not discuss other behavioral traits like rate limits, idempotency, or side effects. Still, the return structure and workflow context make it a 4.

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 concise, with no wasted words. It starts with the main purpose, then gives usage guidance, return format, and clear next steps. Every sentence earns its place.

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 no output schema, the description adequately explains the return structure. It also covers the typical workflow (first tool to use) and references sibling tools for next steps. Parameter details are fully covered in the schema. The description is complete for a list tool in context.

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 coverage is 100%, so baseline is 3. The description does not add any parameter-specific information beyond what the schema already provides via descriptions for limit and offset. No additional meaning is added.

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 'List projects in the WEEEK workspace' with a specific verb and resource. It distinguishes itself from sibling tools by positioning it as the first tool to use for discovery before drilling into boards or tasks, and directly references alternatives for specific details (weeek_get_project) and board discovery (weeek_list_boards).

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 explicitly says 'Use this FIRST when an agent needs to discover what projects exist before drilling into boards or tasks.' It provides clear context for when to use it and when to use alternatives, such as 'For a specific project's full details, use weeek_get_project' and 'For board discovery within a project, use weeek_list_boards next.'

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