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 ("restricted", caller must be the operator and be "proven"). However, it does not describe the effects of the write operations (state transitions, settlement/financial consequences) or idempotency of the tick.

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?

Short and front-loaded, leading with the operator action before the authority/cron details. Backtick markers and the line break are a bit odd but there is no wasted prose.

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 the auth constraint and cron role are covered. Still, for a privileged mutation tool with no annotations, the absence of any explanation of what settling matches actually does leaves the description only marginally complete.

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 coverage is only 50%: npub is documented in the schema, but dpop_token has no description anywhere. The description adds no parameter-level meaning whatsoever, leaving one of two parameters completely opaque.

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 set of actions ("open, close and settle") applied to a resource ("matches"), and explicitly frames the tool as the operator/cron entry point. It is clearly distinguishable from sibling check_now, though "matches" and "settle" are left undefined.

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?

It gives a clear usage condition ("cron entry point") and names the alternative ("check_now is the same work without authority"), telling the agent when to prefer each. No explicit when-not guidance beyond the authority distinction.

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