vault_decline

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

No annotations are supplied, so the description carries the full disclosure burden for a mutation operation. It does not say whether declining is reversible, whether a reason is recorded, what permissions are needed, or what happens to the enrollment record afterward; only the word 'Decline' hints at state change.

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 single short sentence is front-loaded and contains no filler, which is good. However, at three words it crosses from concise into under-specified, so brevity here is not fully earning its place.

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 mutation tool with no annotations, no output schema, and an undocumented required identifier, the definition leaves an agent without the information needed to invoke it confidently. It should at minimum explain the request_id source and the effect of declining.

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 single required parameter request_id has 0% schema description coverage, and the description adds nothing about its meaning, format, or where to obtain it. The only clue is the 32-character length constraint in the schema, which the description never reinforces or explains.

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 states a specific verb and resource ('Decline an enrollment'), which is enough to tell it apart conceptually from vault_begin_enrollment as the opposing action. It does not explain what an 'enrollment' is in this vault context, but the action itself is unambiguous.

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 decline versus when to use vault_begin_enrollment, vault_select_target, or any other sibling. No prerequisites, no conditions, and no exclusions are stated.

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