project_open

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, so the agent knows this mutates state. The description adds nothing beyond that: it does not explain what "isolated" means, what happens on a repeat call given idempotent=false, whether existing state is affected, or what error conditions exist.

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 single sentence is front-loaded and free of waste, but it is terse to the point of under-specification rather than efficiently concise. Brevity here comes at the cost of the information the agent needs.

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 non-idempotent mutation with two undocumented required parameters, no output schema, and a near-identical sibling (project_resume), far more context is needed. The agent cannot predict the effect of a second call or the meaning of either argument.

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% for both parameters, and the description does not compensate. It never explains the distinction between `project` (pattern-constrained identifier) and `name` (free-form string up to 8000 chars), leaving the agent to infer which is the key and which is the label.

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?

"Create/open an isolated project" names the resource (project) but pairs two verbs whose difference matters, and never clarifies whether this creates a new project or attaches to an existing one. It also gives no signal to distinguish it from the sibling project_resume, which sounds like the same operation.

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?

There is no statement of when to use this tool versus project_resume, scope_register, or any other sibling, and no prerequisites or conditions for calling it. The agent must guess the intended context entirely.

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