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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this mutates state. The description hints at overwrite by telling the agent to read the current value first and caps input at 1000 characters, but it never says out loud that the existing context is replaced wholesale rather than merged or appended — the single most important behavioral fact for a destructive write.

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 purpose and constraints are front-loaded and efficient, but the final sentence about how to name projects and locales in replies is a server-wide formatting convention rather than tool-specific information and dilutes a description that should focus on this call. Slightly over-sized for a two-parameter setter.

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?

An output schema exists, so return values need no explanation, and the character limit plus read-before-write pointer are present. What is missing is the overwrite/merge semantics of a destructive write — the one thing an agent cannot infer from the schema or annotations alone.

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 100%, so the baseline is 3, but the description adds real meaning the schema lacks: it explains what the 'context' string should contain (product description, audience, tone) and clarifies via the UUID/locale note that the 'project' value is an identifier used only in tool calls, never shown to users.

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?

States a specific verb and resource ('Set a project's project-wide context') and immediately defines what that context is (free-text prompt guidance shared across every target language — product, audience, tone). This clearly separates it from siblings like set_style_guide and set_repository_patterns, which set other artifact types.

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 clear read-before-write workflow by naming get_project as the way to inspect the current value, and states the scope constraint (shared across all target languages) and the 1000-character limit. It does not explicitly say when to prefer this over set_style_guide, so it falls short of full alternative routing.

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