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

Goes beyond the annotations (which only cover idempotent, non-destructive, non-read-only) by disclosing that unrelated settings are preserved, that unknown keys are rejected, and that credit-spending gates (ai_review, sast, bola) default OFF when absent while others default ON. This defaulting behavior is exactly the kind of thing an agent would otherwise get wrong. It lacks detail on error behavior or the response payload.

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?

Four short sentences, front-loaded with the action and immediately followed by the where and the constraints. No filler or repetition of the title.

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 nested-object mutation with no output schema, the description covers location, validation, preservation and defaults well. It doesn't indicate whether the tool returns the resulting gate state or how partial failures are reported, which would have made it fully self-sufficient.

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 meaning the schema does not encode: the omitted-key default rules that differ per gate class. That is genuinely useful for constructing a correct `gates` map, though it doesn't restate the recognized key list (schema does) or add anything about `context`.

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 ('Toggle') and a precise resource ('PR-pipeline gate flags on a project'), and locates the state under project.test_frameworks. An agent can distinguish this from update_project, which handles other settings, without opening either schema.

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?

Explains the context of use (gates control which checks run on each pull request) and the constraint that only known gate keys are accepted, with the rest of the settings preserved. It does not explicitly name an alternative for editing non-gate settings (e.g., update_project), so it stops short of full when/when-not guidance.

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