GetObjectVersionSource

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

The description includes '[read-only]' tag, indicating no destructive side effects. No annotations are provided, so the description covers the safety profile adequately but could elaborate on return format or permissions.

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?

Extremely concise: one sentence plus a short instruction. No extraneous information; every word adds value.

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 is minimal and sufficient for basic usage, but given no output schema, it could explain what the returned source code contains. However, context signals show no output schema, so it is adequate.

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 description coverage is 100% for both parameters. The description adds the instruction to use content_uri from GetObjectVersions, which is already in the schema description. Since high coverage, a score 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 it fetches source code of a specific object version, using a content_uri from GetObjectVersions. The verb 'Fetch' and specific resource 'source code' are well-defined, and it distinguishes from type-specific version source tools by being generic.

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?

Explicitly instructs to pass the content_uri from GetObjectVersions, providing clear usage context. However, it does not mention when not to use or alternative tools, but the instruction is sufficient.

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