create_shortcut

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that a shortcut is created; it does not mention permissions, whether duplicate titles are allowed, whether the filter must be valid CEL, or what the result of the operation is. This is minimal behavioral information for a mutation.

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, front-loaded sentence with no filler. The parenthetical '(saved filter)' earns its place by clarifying the resource type. It is concise, though it sacrifices some useful behavioral context for brevity.

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?

With no annotations and no output schema, the description should supply more context about side effects, return values, and prerequisites. The schema tells an agent what parameters to send, but it does not explain the operational context, such as needing a connected instance or what success looks like. A create operation needs more than this.

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 baseline is 3. The description adds a small amount of semantic context by calling the shortcut a 'saved filter,' which suggests how 'filter' is used, but it does not provide meaningful additional parameter-level details beyond the schema.

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 the verb ('Create'), the resource ('a new shortcut'), and clarifies the concept by explaining it as a 'saved filter.' This distinguishes it from update_shortcut, list_shortcuts, and delete_shortcut without ambiguity.

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?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites like connecting to an instance first, and no indication of when a shortcut should be created rather than updated or listed. The usage context is entirely absent.

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