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

With no annotations, the description carries the full burden. It usefully discloses the authorization requirement and the system-reservation constraint, but says nothing about reversibility, side effects on the reserved graph, or the response of the operation.

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 short sentences, front-loaded with the permission requirement, with the id source and the constraint each stated once. No padding.

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 one-parameter mutation tool with no annotations and no output schema, the description covers who may call it, where the id comes from, and the main hard constraint. Missing only expected outcome/return behavior, which is a minor gap at this complexity.

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 0% and the single parameter is undocumented in the schema, so the description must compensate. It clarifies that the id identifies a reservation and directs the agent to brainkb_list_reserved_graphs to find valid values, which adds real meaning beyond the bare 'Reservation Id' title.

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?

States a specific verb and resource ('Remove a reservation by its id'), which is the exact inverse of the sibling brainkb_reserve_graph. The cross-reference to brainkb_list_reserved_graphs makes the tool's role unambiguous relative to its siblings.

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?

Gives an explicit caller restriction ('Admin/SuperAdmin'), points to brainkb_list_reserved_graphs as the way to obtain the required id, and states an exclusion ('System reservations cannot be removed'). It stops short of naming an alternative tool or describing failure behavior for system reservations.

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