create_embed

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

With no annotations, the description carries the full burden and does not disclose whether the URL must be oEmbed/embed-compatible, what permissions are needed, or what happens on unsupported URLs. It only restates the mode enum values.

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 action. Nothing wasted, though the mode clarification is placed without context on why the choice matters.

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?

An output schema exists, so return values needn't be explained, but a 13-parameter creation tool with no annotations and zero schema descriptions warrants far more than a one-line description. The agent has almost no basis for filling in required x/y/board_id semantics or optional sizing/metadata fields.

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% across 13 parameters, and the description only explains the 'mode' enum (inline vs modal). Positional parameters (x, y), sizing (width, height), and oEmbed metadata fields (provider_url, preview_url, parent_frame_id) remain entirely unexplained.

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 ('Create an embed item from a URL'), which is clearly distinguishable from siblings like create_card or create_image_from_url. However it does not acknowledge the closely related update_embed sibling.

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?

No guidance on when to use this tool versus alternatives such as create_document_from_url, create_image_from_url, or update_embed for existing embeds. The only guidance-like text concerns the mode values, not tool selection.

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