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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low. The description still adds value by noting the content can be served through an 'authenticated immutable version resource' and that full content is returned inline, which tells the agent about auth requirements and version immutability.

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?

Two short sentences with the main capability front-loaded and the sibling exclusion trailing. No filler or repetition.

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?

With an output schema present and full parameter documentation, the description covers what is needed to invoke the tool correctly. The only meaningful gap is not distinguishing itself from adjacent artifact readers.

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%, including the versionId default and artifactId alias/URL formats, so the schema does the heavy lifting. The description only reinforces 'complete' content and the version-resource concept, adding little beyond the structured fields.

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?

States a specific verb and resource ('Read complete file content') and clarifies the two access modes (inline vs authenticated version resource). It partially disambiguates from siblings by ruling out tables, but leaves the distinction from artifact_read/artifact_get unexplained.

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?

Gives one explicit routing rule ('Use table_get_rows for tables') and implicitly covers version selection via the versionId default. However, it offers no guidance against the much closer siblings artifact_read and artifact_get, so an agent still has to guess which artifact-reader to pick.

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