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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context the annotations lack: the required permission scope and editor role. It does not disclose what happens on a duplicate URL, whether an existing primary URL is replaced, or whether the call is additive, which matters for a non-idempotent 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?

Two short sentences with zero filler. The action and scope come first, and the permission requirement follows as a compact constraint. Nothing is repeated from the schema or annotations.

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 5-parameter non-idempotent write with no output schema, the description covers purpose and authorization but leaves behavioral gaps: duplicate handling, whether primary overrides an existing main URL, and what is returned. Annotations carry the safety profile, so this is adequate but not complete.

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 80%, so the schema already documents url, primary, project and environment. The description only adds the notion that the target may be a project or a single environment, which loosely maps to the optional environment parameter. With the schema doing the heavy lifting, baseline 3 applies.

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 gives a specific verb and resource: 'Record where a project (or one environment) is deployed.' That is concrete enough for an agent to know this stores a deployment URL, and the parenthetical clarifies the optional environment scope. It does not name or contrast any sibling tool, so it stops 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 description states prerequisites ('Requires projects:write and the editor role') but gives no when-to-use versus when-not-to-use guidance and no alternatives. Usage is implied by the verb 'Record' rather than explained, which is the definition of minimum viable.

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