export_update_set

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds no further behavioral details (e.g., permissions, response size, rate limits). It aligns with the read-only annotation, and there is no contradiction, but the description is minimal in extra behavioral context.

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, front-loaded sentence that immediately conveys the action and object. The '[Scripting]' tag is a minor addition but does not add unnecessary bulk. It is concise and well-structured.

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?

This is a simple tool with one parameter and no output schema. The description adequately indicates the return type (XML payload) and the migration context. While it could mention prerequisites or confirm the exact format, it is largely complete for the tool's simplicity.

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 fully describes the single parameter sys_id as 'Update Set sys_id', and the description does not add any further meaning beyond that. With 100% schema coverage, the baseline of 3 is appropriate.

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 retrieves the XML export payload for an Update Set, which is a specific and distinct purpose. The verb 'Get' is precise, and the resource is well-defined, setting it apart from sibling tools like list_update_sets or preview_update_set.

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 mentions the use case 'as used in migration', which implies when it might be appropriate. However, it does not explicitly contrast with alternatives like preview_update_set or list_update_sets, so there is no clear exclusionary guidance. The usage context is implied rather than detailed.

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