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

Annotations already provide idempotentHint=true and destructiveHint=false, and the description adds meaningful context: writes are atomic ('in one transaction'), include provenance, and never overwrite applicant-supplied values. This goes beyond the annotations and clarifies the safety semantics.

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 concise sentence that front-loads the most important behavioral fact (idempotence) and avoids redundancy. It could be improved by naming the source and target, but there is no waste.

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 write operation with an output schema and annotations, the description still leaves key context missing: what data is hydrated, how formationId and applicationId relate, and how this differs from the preview or cap-table hydration flows. An agent would need to inspect sibling tools or schemas to understand the intended use.

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 100%, but the parameter descriptions only say 'UUID value wrapper' and provide no semantic meaning. The tool description adds no information about applicationId or formationId, so the agent must infer roles from the tool name. Baseline of 3 is appropriate given full schema coverage.

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 states the tool writes values and provenance in one transaction, but does not explicitly say what values are hydrated, from what source, or into what target. The name suggests 'from formation,' but the description itself is vague about the resource and scope, and does not distinguish it from banking_hydrate_from_cap_table.

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 is given for when to use this tool versus alternatives such as banking_preview_formation_hydration or banking_hydrate_from_cap_table. The idempotence note is useful but does not help an agent decide between sibling hydration tools.

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