Reserve

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

Annotations already flag readOnlyHint=false, idempotentHint=false, and destructiveHint=false, but the description adds genuinely useful behavior beyond them: the tool never mints or reuses an id locally, and every mutating action refuses with a named dependency_blocked/ConceptAuthorityUnavailable error when the authority is absent. That failure-mode disclosure is exactly the kind of context annotations cannot convey.

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 first line is well front-loaded, but the following paragraph spends several sentences on internal architecture (port injection, agent_connector_sdk.governance path) that an agent does not need in order to invoke the tool. The behavioral payload could be stated in one sentence instead of a paragraph.

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, and annotations plus the failure-mode note cover the mutation profile. However, the schema exposes list/verify/release/reconcile parameters on a tool named 'reserve', and the description never resolves whether this is a single-action or dispatcher tool, leaving a real ambiguity for the caller.

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 all 26 parameters carry their own 'For reserve/For list/For verify_candidate' descriptions, so the schema does the heavy lifting. The prose description adds no parameter-level meaning (e.g., what request_key_ref idempotency does or what namespace must contain), so the baseline 3 applies.

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 opening line 'Reserve (rm_concepts). Concept-id claim coordination against RMDD-16's central authority' does name a verb (Reserve) and a resource (concept-id claim), but the rest of the description is architectural prose about port injection rather than clarifying what the tool concretely does. It never distinguishes itself from siblings like rm_concepts_get, rm_concepts_list, or rm_concepts_release, which the schema's 'For list:/For get:' parameters clearly imply exist.

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 when-to-use guidance: nothing tells the agent when to call reserve rather than rm_concepts_list, get, release, or materialize. The only conditional statement is about the authority being unavailable, which is a runtime failure mode, not selection guidance.

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