project_open

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds value by noting 'existing' (implying a valid path is required) and 'compact current state' (indicating a reduced, summarized output), but it does not disclose potential errors or the meaning of 'compact' in detail. No contradiction with annotations.

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, front-loaded sentence that is concise and free of redundant content. Every word contributes meaning, making it efficient and easy to parse.

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 tool's simplicity (one parameter, rich annotations, and an output schema), the description is adequately complete. It states the core action and expected return. However, it could be enhanced by mentioning behavior on non-existent paths or the use of the tool as a prerequisite for other project operations, but these are not critical given available structured metadata.

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 description coverage is 0%, so the description must compensate for explaining the 'path' parameter. It only implies that path points to an existing project, but provides no details about format, absolute vs. relative, or accepted project types. This is minimally helpful beyond the parameter name.

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 action ('Open') and the specific resource ('existing Garment Project'), and specifies the outcome ('return compact current state'). This distinguishes it from siblings like project_create, project_import, and project_status by conveying the intent to load an existing project rather than create, import, or merely query status.

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 implies when to use the tool (to open an existing project) but provides no explicit guidance on alternatives or exclusion criteria. With siblings like project_status and resource_read, the description does not clarify when to prefer this tool over them, leaving usage context somewhat ambiguous.

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