project_close

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

Description discloses key behavioral effects (stops nodes, frees resources), but lacks details on prerequisites (e.g., must be open), idempotency, error states, or reversibility. No annotations exist to supplement.

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?

Single sentence, front-loaded with verb and resource, no wasted words.

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?

Adequate for a simple close action, but output schema exists (not shown) and no annotations; missing details like error handling, synchronous behavior, and relation to sibling lifecycle tools.

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?

Only one parameter (project_id) with 0% schema description coverage; the description adds no explanation of this parameter's purpose, expected format, or behavior when null.

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?

Description clearly states the action (close), the target (open project), and effects (stops nodes, frees resources). It distinguishes from sibling tools like project_open and project_delete.

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?

Implicit usage context is clear (close open project), but no explicit guidance on when to use vs alternatives like project_delete or project_stop, and no when-not-to-use information.

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