Update project

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false. Description adds that this is a PATCH request (mutation). No additional behavioral details like authorization needs, rate limits, or side effects beyond the update. Adequate but minimal extra value.

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?

Three sentences; first two are redundant ('Update project. Update the details of a project.'). Could be merged. The rest is useful. Slightly verbose but acceptable.

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?

Tool has two parameters, no output schema, and simple function. Description covers purpose and basic distinction from sibling, but lacks parameter details, return value, and behavioral context. Sufficient for a simple update but not comprehensive.

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%, but description provides no parameter explanations. The schema lists 'name' and 'projectId' but their meaning and usage are not clarified. Agent must infer from schema alone. Should have described required projectId and optional name update behavior.

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?

Clearly states the tool updates a project, distinguishes from updating an environment with a sibling tool reference. Specific verb 'Update' and resource 'project' are used. The call to `PATCH /projects/{projectId}` reinforces purpose.

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?

Explicitly says when to use this tool (update project) and when to use an alternative (Update environment for environment updates). Provides a link to the endpoint documentation for context. No prerequisites or exclusions mentioned, but the guidance is clear.

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