Set project

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

Annotations already declare readOnlyHint=false and idempotentHint=true, establishing this as a non-destructive, repeatable mutation. The description adds useful behavioral context beyond those annotations: the change takes effect without redeploying. No contradiction with the annotations exists.

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 two short sentences with every clause earning its place: the core action, the null clearing behavior, and the no-redeploy effect. It is front-loaded and contains no filler or repetition.

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 simple two-parameter setter with full schema coverage and helpful annotations, the description provides enough context to call the tool correctly. It does not describe return values, but the absence of an output schema and the simplicity of the mutation make that a minor gap.

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 100%, so both parameters are already documented with their types and meanings. The description adds minimal semantic value beyond the schema, only reinforcing that null clears the project, which the schema already states. A baseline 3 is appropriate because the schema carries the parameter documentation burden.

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: file a deploy under a project or pass project=null to clear it. It is specific about the resource and operation, and the title 'Set project' reinforces the intent. It does not explicitly name sibling tools like deploy or catalog to differentiate from them, so it falls short of a 5.

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 phrase 'Takes effect without redeploying' implies this is the tool to use when changing a deploy's project assignment without rebuilding or redeploying. However, the description never states when to choose this tool over alternatives such as deploy or catalog, leaving the usage context implicit rather than explicit.

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