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

Annotations already declare non-read-only, idempotent, non-destructive, and the description usefully adds the authorization requirement (projects:write + owner role) that annotations cannot express. It omits key mutation behavior: whether unspecified fields are left untouched, whether renaming requires uniqueness, and whether a null description clears the field even though the schema permits null.

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?

Two short sentences, zero filler. The action is front-loaded and the permission requirement follows immediately, so an agent gets capability and gate in one read.

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?

A small three-parameter mutation tool with annotations covering the safety profile and no output schema, so the bar is modest and mostly met. Still missing are the partial-update contract and null-description handling, both of which affect how the agent shapes the call.

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 coverage is only 33%, with the 'project' parameter documented as slug or id but 'name' and 'description' carrying no schema descriptions. The description partially compensates by mapping name→rename and description→change, but it never clarifies the nullable description (clear vs. no-op) or partial-update semantics for omitted parameters.

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?

Names a specific verb (rename / change description) and the resource (project), which cleanly separates it from create_project, get_project, list_projects and delete-style siblings. It is narrower and more concrete than the title alone, though it never explicitly contrasts itself with any sibling.

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?

Gives a real prerequisite (projects:write plus the owner role), which is genuine when-to-use information. It does not say when not to use it, nor whether an agent should prefer other tools for broader project edits, so guidance is implied rather than explicit.

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