lattice_create_backup_destination

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

No annotations are provided, so the description carries full burden. It only states the action and config details but does not disclose side effects, required permissions, uniqueness constraints, or what the response contains. For a mutation tool, this is insufficient.

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 extremely concise with two sentences, no fluff. Every sentence adds information: the first states the action, the second clarifies the config parameter's nature. It is appropriately sized and front-loaded.

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 create tool, the description omits expected output (e.g., returns created destination), prerequisites, or constraints. With no output schema, the description should at least hint at the return value. It also does not address error conditions or idempotency, leaving gaps for an AI agent.

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%, but the description adds significant value by explaining that 'config is a free-form object whose shape depends on type' and provides a concrete example (S3 with bucket, region, endpoint, credentials). This guides the user beyond the generic schema description.

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 'Create a backup destination' using a specific verb+resource. It distinguishes from sibling CRUD tools like list, get, update, delete by focusing on creation. The example of config shape further clarifies the purpose.

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 implicitly indicates when to use (to create a new backup destination) but does not explicitly mention alternatives or prerequisites. Given the tool name and context, it is adequate but lacks explicit guidance.

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