share_diagram

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description 'Generate a shareable URL' is consistent with these annotations, but adds minimal additional behavioral context (e.g., whether it creates server-side state or only transforms input). No contradictions.

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?

The description is a single, concise sentence that immediately conveys the tool's purpose. Every word is necessary, and it is front-loaded with the key action.

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 simple tool with one parameter and no output schema, the description combined with annotations is largely complete. It does not explain the URL format or expected usage, but these are minor gaps given the tool's straightforward nature.

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%, and the single parameter 'dgmo' is well-described as 'DGMO diagram markup'. The tool description does not add further meaning beyond what the schema provides, placing it at the baseline.

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 clearly states it generates a shareable URL for a DGMO diagram. It uses a specific verb ('Generate') and resource ('shareable diagrammo.app URL'), and implicitly distinguishes from siblings like 'preview_diagram' and 'open_in_app'.

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 description indicates a clear purpose but provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, restrictions, or when not to use it, which would be helpful given several sibling tools.

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