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

With no annotations provided, the description carries full burden. It discloses that nothing is written without apply, that passwords are redacted, that the proposal includes what was ignored and why, and that apply is all-or-nothing. It also mentions the monitor name travels in emails/dashboard/badge, which is transparent about side effects.

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 description is longer than necessary and repeats the same point twice: 'Without apply=1 nothing is written' appears verbatim twice, and the explanation of the proposal is redundantly restated. While the information is valuable, the redundancy detracts from conciseness.

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?

Given no output schema and no annotations, the description covers all essential aspects: dry-run vs apply behavior, ignored lines, redaction, name derivation, and all-or-nothing semantics. It explains the proposal contents sufficiently, making it complete for an agent to invoke correctly.

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?

The schema covers 67% (apply and crontab have descriptions; guest_token does not). The description adds meaningful context for apply (dry-run vs apply) and crontab (format as text/plain), but does not elaborate on guest_token. It adds value beyond the schema for two of three parameters.

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 clearly states the tool reads a crontab and proposes one monitor per scheduled line, with an optional apply mode. It distinguishes itself from siblings by describing the specific behavior and the dry-run proposal, which no other sibling tool 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?

It explicitly explains when to use apply=1 versus without, states the all-or-nothing semantics, and details which crontab lines are ignored (comments, variables, @reboot) and how @daily shortcuts are handled. This gives clear usage guidance and alternatives.

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