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

Goes meaningfully beyond the annotations, which only say readOnlyHint=false, destructiveHint=false, openWorldHint=false. The description discloses the crucial trait that this is a full replacement, not a merge, so omitted fields are dropped, and it prescribes the read-then-resubmit pattern that prevents data loss. It does not cover permissions, auth, or failure behavior.

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 tight sentences, front-loaded with the mutation semantics and followed by the required workflow. Every clause carries information useful for correct invocation; nothing is wasted.

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 mutation tool with a large nested object and no output schema, the description covers the biggest risk (full replacement) and the correct call sequence, while annotations already cover the safety profile. Remaining gaps are minor: no note on validation-failure behavior or visibility of edits.

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%, so the description must carry the burden for three parameters. It only clarifies that the profile object must be sent whole and only the requested change applied; projectId, siteId, and the 23 required nested profile fields receive no explanation. This is real but partial compensation for a worst-case coverage gap.

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 ("Replace") and resource ("the editable site profile"), so the agent knows this is a full write to the site profile. It does not explicitly contrast with other update tools, but it names get_site_profile, which anchors it as the write counterpart to a known read tool.

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 prerequisite workflow: read with get_site_profile first, then send every field back with only the user's change applied. This tells the agent both when and how to use it. It stops short of naming an alternative for cases where only a partial update is intended or stating when not to use it.

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