GetMetadataExtensionVersions

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

Explicitly marks as [read-only] and enumerates return fields. No annotations, so description carries full burden. Does not disclose auth/rate limits, but read-only is key behavioral trait.

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?

Single dense sentence with no fluff. Purpose, return fields, and follow-up tool are all included. Highly 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?

Adequate for a list tool with one parameter and no output schema. Mentions key fields and next step. Missing pagination/ordering details, but not critical.

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% with a single parameter. Description adds no further semantic value beyond the schema's description. Baseline 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?

Clearly states it lists the version history of a CDS metadata extension, specifying the resource and action. Distinguishes from related tools like GetMetadataExtensionVersionDiff and GetMetadataExtensionVersionSource.

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?

Implies a workflow by mentioning content_uri and GetMetadataExtensionVersionSource, but lacks explicit when-to-use/avoid guidance or differentiation from numerous similar sibling tools.

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