GetMetadataExtensionVersionDiff

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

The description includes a [read-only] hint but does not disclose the output format or any side effects. Since annotations are absent, the description carries the burden but provides minimal behavioral context beyond the read-only hint.

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, well-structured sentence that front-loads the read-only hint and conveys all necessary information without unnecessary words. It is appropriately concise.

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?

The description explains the tool's purpose and input source clearly, but it does not describe the output format. Given the output schema is absent and the tool's complexity is moderate, a brief note on the diff output would improve completeness.

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?

With 100% schema coverage, the description adds value by specifying that content_uris come from GetMetadataExtensionVersions entries and labeling them as OLD/base and NEW/compare. This supplements the schema descriptions.

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?

Description clearly specifies the verb 'Compute a unified diff', the resource 'CDS metadata extension versions', and how to specify versions via content_uris from GetMetadataExtensionVersions. It distinguishes from sibling diff tools by being specific to metadata extensions.

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 implies usage for comparing two metadata extension versions but does not explicitly state when not to use it or mention alternatives. The context is clear but lacks exclusions or comparisons with similar diff tools like GetClassVersionDiff.

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