get_changeset_details

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

No annotations are provided, so the description carries the full burden. 'Fetch' implies a read operation, and the description discloses that it returns the changes (sys_update_xml rows), which is useful behavioral context. However, it does not explicitly state that the operation is read-only, does not mention permissions, error cases, or the full response structure. The description is adequate but not rich in behavioral disclosure.

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, efficient sentence that front-loads the core action and result. Every word contributes value, with no fluff or redundant phrasing. It is concise without sacrificing the key purpose.

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 simple single-fetch tool with one parameter, the description covers the essential purpose and the inclusion of changes. It does not specify the full return structure, but given the lack of an output schema, it still gives enough for an agent to call it correctly. Minor gaps like error handling and response format do not significantly hinder correct usage.

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 100% — the only parameter changeset_id already has a clear description ('sys_id or name of the changeset'). The tool description adds no additional semantic detail beyond the schema; it does not clarify preferred format, validation, or edge cases. Since the schema covers the parameter fully, a 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 states a specific verb ('Fetch'), a specific resource ('a single changeset'), and clarifies that it includes the changes as sys_update_xml rows. This clearly distinguishes it from sibling tools like list_changesets (which lists many), update_changeset (which modifies), and commit/publish (which are mutations).

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?

There is no explicit guidance on when to use this tool versus alternatives. It does not mention that list_changesets is for listing multiple changesets or that update_changeset is for modifications, nor does it state criteria for choosing this tool. The purpose implies it is for retrieving details of a single changeset, but the description leaves this entirely to inference.

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