migrate_secret

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

With no annotations, the description carries the full behavioral burden. It usefully discloses non-exposure, non-overwrite behavior, user review for differing values, and dry-run previews, but it does not clarify what happens to the source secret, required permissions, failure behavior, or return output.

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 front-loaded with purpose, then moves directly into workflow and safeguards. It is appropriately sized and every sentence adds useful 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?

For a complex migration tool with no annotations, no output schema, and zero schema descriptions, the description covers the core workflow but omits important context such as required version semantics, source-secret lifecycle, and result format. It is helpful but not fully complete.

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 0%, so the description must compensate for all six parameters. It explains target_id, field, and dry_run, but leaves the required expected_version, id_or_name, and folder_id unexplained.

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 gives a specific verb and resource: transferring a built-in secret into the vault without exposing its value. It is distinguishable from generic create/update siblings, though it does not explicitly name or contrast them.

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?

It gives an explicit search-first workflow, explains when to pass target_id and field versus when to omit target_id, and states that different values require review and dry_run previews changes. This is strong operational guidance for selecting the right mode.

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