GetMetadataExtensionVersionSource

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

No annotations are present, so the description carries full burden. It marks the tool as [read-only], but does not describe the return format or any other behavioral traits such as side effects or error conditions.

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 sentence, 20 words, front-loaded with the [read-only] hint, and contains no unnecessary information.

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 read-only fetch tool with no output schema, the description references the prerequisite parent tool but does not specify the format of the source returned. Slightly incomplete, but adequate for typical 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?

The only parameter content_uri is fully described in the schema (100% coverage). The description adds no additional meaning beyond restating the schema's description, so 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 fetches the source of a CDS metadata extension version using a content_uri, and references the parent tool GetMetadataExtensionVersions. It distinguishes from siblings like GetMetadataExtensionVersions and GetMetadataExtensionVersionDiff.

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 explains that the content_uri comes from a GetMetadataExtensionVersions entry, providing clear prerequisite context. It does not explicitly state when not to use, but the usage intention is well-defined.

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