confluence_embed_image

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

Clearly states that calling the tool results in an error, and explains why (requires Atlassian Media API, not implemented). Without annotations, this disclosure fully addresses behavioral expectations.

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 sentences, no filler. Front-loaded with the key message ('NOT SUPPORTED'). Every word earns its place, efficiently conveying status, reason, alternative, and consequence.

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 non-functional tool, the description is complete: it states unsupported status, reason, alternative, and outcome of calling it. No additional information is needed.

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?

The input schema has 100% coverage with descriptions, so baseline is 3. The tool description adds no parameter-specific information, but for a stub tool that errors, this is acceptable since parameters are never actually used.

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?

The description explicitly states the tool is not supported and will return an error, clearly distinguishing it from functional tools. It specifies the verb 'embed image' and the resource, and immediately indicates non-functionality.

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?

Directly tells the agent not to use this tool ('NOT SUPPORTED') and provides an explicit alternative ('Use confluence_add_attachment'). This eliminates ambiguity about when to invoke it.

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