Create Embed

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the mutation safety profile is covered. The description adds only that it changes community state and that confirm=true is required, but it does not say what specifically is altered or what a failed/partial call leaves behind. With annotations carrying the safety burden, this is adequate but thin.

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, front-loaded with the core fact and the confirm gate, with no padding. It is efficient, though the first sentence is largely redundant with 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 destructive, non-idempotent creation tool with a nested payload object and three mutually exclusive body-input modes (flags, payload, payload_file), the description explains none of the mode relationships or mutation scope. No output schema exists, but the description still leaves the agent without enough context to invoke it confidently.

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 the schema already documents url, account, confirm, payload, and payload_file. The description 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?

"Create Embed" merely restates the tool name and title, adding only that it "changes community state." It does not distinguish the tool from siblings like get_embed, create_post, or create_image_post, nor does it specify what an embed is in this context (a content block? a URL attachment?).

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 only usage signal is the confirm=true prerequisite for "the user-requested action." There is no guidance on when to use create_embed versus get_embed, create_post, or other content-creation siblings, and no exclusions or preconditions beyond the confirm gate.

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