wordpress_list_backups

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

With no annotations, the description carries full responsibility for behavioral disclosure. It indicates a read operation but does not describe return format, pagination, or whether both database and file backups are included. The lack of any behavioral details beyond the verb 'Get' leaves the agent without important context.

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 a single, short sentence that is immediately clear and front-loaded. There is absolutely no wasted text, making it an exemplar of 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 the tool has no parameters and no output schema, the description is minimally viable but leaves the return structure unspecified. It could benefit from stating that it returns a list of backups with identifiers, types, timestamps, or sizes. The description is adequate for a zero-param list operation but incomplete in describing the output.

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 tool has zero parameters, so the input schema covers everything. The description adds no parameter details, which is acceptable since none exist. Baseline 4 is appropriate because there is no parameter semantics burden.

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 uses a specific verb 'Get' and resource 'all available backups', clearly indicating a read-only list operation. It distinguishes from sibling backup tools like wordpress_full_backup, wordpress_restore_backup, and wordpress_delete_backup by its focus on retrieval only. However, it doesn't explicitly contrast with alternatives, leaving some room for ambiguity about what 'available' means.

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?

No guidance is provided about when to use this tool versus alternatives. The description simply states the operation without mentioning exclusions, prerequisites, or complementary tools. An agent must infer from context that this is for listing backups, but no explicit direction is given.

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