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

The description goes well past the annotations by spelling out the mutation model: empty string clears named text fields, null/"" clears the date, platform maps are merged per key while platforms/tags are wholesale replacements. That is exactly the kind of what-gets-destroyed detail destructiveHint=true alone cannot convey. It stops short of covering failure modes or permission requirements.

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?

Five short sentences, each carrying a distinct rule (scope, partial update, text clearing, date clearing, merge-vs-replace, id source). The most error-prone rule, clearing, is placed early and nothing is repeated.

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 14-parameter mutation tool with no output schema, the description covers the semantics an agent would most likely get wrong (clearing, merging, replacing) and points to the id source. It does not say what the response contains or what happens with an invalid status/content_type value, which is a minor remaining gap.

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 cross-parameter meaning the schema does not: it enumerates which fields are clearable via empty string (description, caption, first_comment, youtube_title) and contrasts merge semantics for platform maps against replace semantics for lists. Some of this duplicates the schema's own "Replaces the tag list" wording, so it is not purely additive.

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 ("Edits a content concept on the Concepts board"), which is enough to separate it from update_post or create_concept. It never names a sibling explicitly, so the boundary with update_post is inferred rather than stated.

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?

"Pass only the fields to change" is explicit usage guidance for a PATCH-style tool, and "Get concept ids from list_concepts" removes the main precondition hurdle by naming the sibling that supplies ids. There is no explicit when-not or alternative-selection rule (e.g. versus update_post), which keeps it below a 5.

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