akb_publication_snapshot

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

Discloses key behaviors: saves result to S3 and switches mode, but lacks information on prerequisites (e.g., publication must exist in 'table_query' mode), reversibility, or permission requirements. With no annotations, the description carries the full burden but only partially fulfills it.

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 concise sentences front-load the primary action and detail the result. 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?

Covers the core action and parameters, but omits output behavior (e.g., whether it returns a status) and potential prerequisites. For a tool with no output schema, more detail on response or side effects would improve 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?

Both parameters have schema descriptions ('Vault name', 'Publication slug') providing clear meaning. The tool description adds no further context beyond the schema, so 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?

The description uses a specific verb ('Create') and resource ('snapshot of a table_query publication'), clearly stating the action and result (saves to S3, switches mode). It distinguishes from siblings like akb_publications and akb_publish by focusing on the snapshot operation.

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 on when to use this tool versus alternatives (e.g., akb_publish, akb_publications). The description only states the action without context for selection.

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