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

The description adds real context beyond annotations: partial-update behavior and profile-vs-organization targeting. But with destructiveHint=true, the highest-value missing detail is what actually gets destroyed or replaced — e.g. whether passing `categories` replaces the existing list or appends to it. That gap is left entirely to the schema.

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?

Three tight sentences, zero waste. The core action and update semantics come first, then the targeting default and the sibling pointer — properly front-loaded.

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?

There is no output schema, so the description would need to carry return behavior; it does not describe the response. Combined with an unexplained destructiveHint=true and no statement about merge-vs-replace semantics for list fields, the definition is adequate but leaves real behavioral questions unanswered.

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 100%, so all five parameters are already documented in the schema, including the `organization` default. The description repeats the org-targeting rule but adds no syntax or format detail beyond the schema, so the 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?

States a specific verb and resource ('Updates the metadata of a published post') and enumerates the mutable fields (marketing objective, categories, favorite). The word 'published' implicitly separates it from the sibling update_draft, so an agent can route correctly without opening a 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 partial-update semantics ('Only the provided fields are updated') and gives a clear default-vs-alternative rule for targeting: personal profile by default, pass `organization` for a company page, with a pointer to list_organizations. It stops short of explicit when-not-to-use guidance or preconditions.

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