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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint. "Read-only, runs straight away" largely restates that safety profile, though "runs straight away" usefully signals there is no queue or approval step. Nothing is said about what schedule fields come back or how many schedules may exist.

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?

Two short sentences, purpose first, with the site constraint attached directly to the verb. "Through Royally" is jargon that carries little information but the rest is free of padding.

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?

For a single-parameter read-only list tool with full schema coverage and rich annotations, the description covers the basics. What is missing is disambiguation from the several near-duplicate backup-listing siblings, which is the main thing an agent needs here.

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 single parameter is an enum with exactly one allowed value, so the schema fully documents it. The parenthetical "(site: demo.royalplugins.com)" only echoes the enum label already in the schema, adding no meaning beyond it.

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?

"List backup schedules" gives a specific verb and resource, and the parenthetical names the only site it applies to. It does not distinguish itself from the closely related siblings sv_get_backups, sv_get_backup_status, or updraftplus_get_schedule, so an agent has no basis for choosing among them.

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?

The description never states when to use this tool rather than sv_get_backups, sv_get_backup_status, or updraftplus_get_schedule, nor any prerequisite or exclusion. The only usage-adjacent remark, "runs straight away," is about call behavior, not tool selection.

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