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

readOnlyHint=true already declares the safety profile, so 'Read-only' is largely redundant. The description earns credit for two genuine extras: the 'newest first' ordering trait and the availability constraint ('only offered when backups are enabled'). Pagination/defaults are left to the schema.

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-loaded with the operation and scope, then the use case and precondition. The CLI-twin parenthetical is arguably extra, but it is short and helpful for orientation; no wasted sentences.

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 7-param read-only list tool with no output schema, the description covers purpose, ordering, and availability. An agent has enough to call it correctly; the only minor gap is pagination behavior, which the limit parameter largely covers.

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 100%, so all seven parameters are already documented. The description only restates the 'backup, restore and clone' enum values and adds no format or syntax detail beyond the schema — baseline 3 applies.

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 (list) and resource (backup/restore/clone data runs), plus scope and ordering ('newest first'). The parenthetical CLI twin (`ankra runs list --kind backup`) anchors the mental model, and the plural 'list' clearly separates it from the singular get_data_run sibling.

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?

Gives clear context for use ('answer what a backup did, and when one failed') and a gating precondition ('Only offered when backups are enabled'). It stops short of naming the alternative (get_data_run) for fetching a single run, so no explicit when-not guidance.

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