summarize_project_backup

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

The verb 'summarize' suggests a read-only operation, but no annotations are provided to confirm non-destructive behavior. The description lacks explicit statements about side effects or safety, leaving some ambiguity.

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 very concise and well-structured with a one-line summary, Args section, and Returns section. No extraneous information.

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 presence of an output schema, the description adequately covers the tool's purpose and return value content. However, it could elaborate on the structure of the backup input parameter for completeness.

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 description adds value by labeling the single parameter as 'Backup payload to summarize' despite 0% schema description coverage. This clarifies the parameter's purpose beyond the schema's minimal definition.

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 it summarizes a project backup, with specifics about what it returns (counts, names, secret-reference indicators). It distinguishes from sibling tools like backup_project or restore_project_backup which perform different actions.

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 explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, typical workflow order, or scenarios where it should be used.

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