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

Annotations already declare destructive/openWorld/non-idempotent, and the description adds real value beyond them: it states it does not authenticate a principal, read a ledger, persist permissions, or grant execution authority, and it discloses error behavior ('unavailable or non-JSON backends produce tool errors'). It leaves some tension with destructiveHint=true unaddressed, but the added boundary detail is substantive.

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 text is long and repetitive, opening with 'Unavailable historical backend' rather than the tool's function, and restating negation ('grants no authority' / 'never supplies server credentials'). Several sentences do earn their place (the operating boundary, the error behavior), but front-loading and redundancy are poor.

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 output schema and a free-form additionalProperties body, the description must carry the burden; it supplies auth, boundary, and error context but leaves the core purpose and the 'mode' contract ambiguous. It is serviceable but not complete enough for confident invocation.

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% for the single 'mode' parameter, so the description must compensate. It partially does ('Supply its documented mode, arguments, and required signed authority or grant') but never enumerates valid modes or the shape of the body, leaving the opaque string under-specified.

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 does name a verb+resource ('previews a permission decision') but immediately undercuts it with 'Unavailable historical backend' and a second, contradictory framing ('Track what an agent is allowed to do...'). It never cleanly distinguishes itself from siblings like wever_agent-allowance-console or wever_delegated-authority, so an agent cannot confidently tell what this does.

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 / when-not-to-use guidance and no mention of any alternative among the ~26 sibling tools. The only conditional content is about credentials and backend availability, not about tool selection.

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