heddle_edge_snapshot_capture

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

With no annotations provided, the description carries full burden. It discloses that mutations are scoped to .weft/heddle state and mentions a server config for the loomweave command, but does not address idempotency, side effects, dry_run behavior, or other behavioral traits beyond the basic mutation claim.

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 sentences, directly stating purpose and a key constraint. No redundant information, but a slightly more structured format (e.g., bullet points for key behaviors) could improve scannability.

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 8 parameters, no annotations, and an output schema (unseen), the description is insufficient. It does not explain parameter usage, return values, or provide enough context for an agent to correctly invoke the tool without external knowledge.

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%, meaning no parameters are described in the schema. The description adds no information about parameters; it only mentions capturing edges without relating to any of the 8 parameters defined.

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?

Description clearly states the tool captures 'dated loomweave edges' into a specific store and distinguishes from sibling tools by noting it only mutates .weft/heddle state. However, the term 'loomweave edges' is domain-specific and may be unclear to some agents.

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?

Description mentions that the tool never mutates a sibling repo, providing a hint about when not to use it, but it lacks explicit guidance on when to use this tool versus alternatives like 'capture_snapshot' or 'heddle_change_list'. No explicit when/when-not or alternative recommendations.

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