export_update_set

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, fully disclosing that the tool is a safe, read-only, idempotent operation. The description adds minimal context beyond annotations ('as used in migration' and '[Scripting]'), providing some behavioral context without contradicting the annotations.

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 with an additional bracketed note. Every word serves a purpose—no redundancy, no filler. It is appropriately front-loaded and efficient.

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 that the tool is a simple read operation with one parameter and safety is fully covered by annotations, the description is nearly complete. It states the output format (XML) and usage context (migration). Minor gaps include lack of error conditions or return structure details, which are less critical given the tool's simplicity and annotation coverage.

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?

The input schema already describes the single parameter 'sys_id' with a clear description ('Update Set sys_id'), achieving 100% coverage. The tool description does not add any additional meaning or clarification beyond what the schema provides, so it meets the baseline expectation.

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 it retrieves the XML export payload for an Update Set used in migration. It specifies the action ('Get') and resource ('XML export payload'), which is distinct from siblings like preview_update_set or list_update_sets. However, it does not explicitly differentiate from these sibling tools, which would elevate it to a 5.

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 provides no guidance on when to use this tool versus alternatives such as preview_update_set or get_current_update_set. It mentions 'as used in migration' but lacks explicit when-to-use or when-not-to-use instructions, and does not list any prerequisites or exclusions.

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