Create Short Url

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

Annotations already declare the write/non-idempotent/closed-world profile, so the bar is lower. The description adds real context beyond that: the Technical-Preview API status, where the created slug resolves (/s/<space>/goto/<slug>), and the space-routing consequences of path prefixes. It does not call out that repeated calls produce distinct slugs (relevant given idempotentHint=false), which keeps it from a 5.

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?

Purpose is front-loaded and each subsequent sentence carries a distinct, non-redundant rule about space/prefix handling. The middle section is dense and reads as an undifferentiated block of edge cases rather than being broken into clean, scannable statements.

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 need not be explained. For a preview mutation tool with a free-form params object, the description supplies the space semantics, locator pattern, and resolution behavior an agent needs to call it correctly; only the non-idempotency implication is left implicit.

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?

With 0% schema description coverage the description must carry the load, and it does: it documents locator_id (LEGACY_SHORT_URL_LOCATOR), the expected params shape ({'url': '/app/...'}), and the space parameter's prefix interaction rules. It is not exhaustive, though, since params is an open object (additionalProperties: true) and no keys beyond url are described.

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?

Opens with a specific verb+resource ('Create a Kibana short URL') and immediately distinguishes itself from the sibling resolver by naming resolve_short_url as the consumption side. An agent can tell what this does and how it relates to sibling tools without opening the schema.

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?

Provides substantial conditional guidance on correct invocation (when space is set, drop the /s/<space> prefix; a /s/<id> path without space lands in the default space), which is genuinely useful. However, it never states when to prefer this tool over alternatives or any exclusion, so tool-selection guidance is only implied.

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