athena_topology_rollback

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

With no annotations, the description carries the full burden of behavioral disclosure. It does mention two important behaviors: the rollback operates under 'current-version CAS' (implying concurrency checks via expected_version) and that the rollback is preserved as a 'new witnessed transaction.' However, it omits side effects, permissions, error conditions, and return behavior, leaving significant ambiguity for a mutation tool.

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, action-oriented sentence with no wasted words. It front-loads the primary verb and resource, then packs two key constraints (CAS and witnessed transaction) into a compact phrase. The terminology is dense but appropriate for a specialized tool.

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 complexity of CAS, witnessing, and topology transactions, plus the absence of annotations and output schema, a one-sentence description is insufficient. It does not explain return values, failure modes, parameter semantics, or how exactly the CAS/witness behavior works, leaving the agent with many unknowns for safe invocation.

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 0%, and the description does not explain any of the four parameters (topology_id, txid, expected_version, actor). While 'current-version CAS' hints at expected_version's role, none of the parameters are defined, making it impossible for an agent to understand how to populate them correctly without external knowledge.

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 the tool's function—rolling back a prior collective topology transaction—and differentiates it from sibling tools like athena_policy_rollback by specifying 'collective topology' and the CAS/witnessed transaction context. The verb 'Rollback' and the resource 'prior collective topology transaction' make the purpose unambiguous.

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 implies the use case (rolling back a prior collective topology transaction under current-version CAS) but does not explicitly state when to use this tool versus alternatives like athena_policy_rollback or athena_topology_apply. It also lacks explicit exclusions or conditions, so usage guidance is inferred rather than spelled out.

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