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

Goes well beyond the annotations: it discloses that the effect is enqueue-only (actual push waits for the cron tick), that the scan is budget-limited and resumable via the 'complete' flag, that only Paid accounts are reconciled and lapsed mirrors are paused, and that GitHub rows queue but never push. That is exactly the mutation semantics an agent needs given destructiveHint=true and openWorldHint=true.

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?

Front-loads the action, then the trigger condition, then return shape and constraints; nearly every clause carries information. It is dense and slightly run-on, packing account tier, provider behavior, and return semantics into a single 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?

There is no output schema, and the description compensates by naming all four return fields and explaining that complete=false means a budget-truncated resumable scan. Account requirements, provider limitations, and side-effect timing are all covered, so nothing material is missing.

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 100% and the enum is documented, so the provider parameter is already fully specified. The description adds relevant semantics (gdrive works, github is queued but never pushed, omit for all) but never references the parameter name directly, so this is baseline-level rather than additive.

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 ('manually trigger a mirror reconciliation pass') and explains the mechanism precisely: enqueues unseen memories and re-marks changed ones for the next cron tick. This implicitly separates it from muninn_mirror_push (immediate push) and muninn_mirror_status, but no sibling is named explicitly, so an agent must infer the boundary.

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?

'Useful after a gap or error' gives a clear triggering condition, and the account/paused and GitHub-not-pushed notes tell the agent when this will do nothing. There is no explicit exclusion or named alternative (e.g., 'use muninn_mirror_push for an immediate push'), so usage is well-contextualized but not fully routed.

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