get_artifact_content

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

Annotations already declare readOnlyHint=true, and the description aligns with this. The description adds the behavioral constraint that it only works for text/json files, which is valuable beyond the annotation. However, no other behaviors (e.g., file size limits, error handling) are disclosed.

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 extremely concise with a single phrase, containing no redundant information. It is front-loaded with the core action. However, it could be slightly more structured with separate sentences for purpose and parameter hints.

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?

Given the tool's low complexity (read only, 2 params, output schema exists), the description covers the basic purpose and file type constraint. However, it lacks parameter documentation and sibling differentiation, making it incomplete for effective agent selection.

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 0% schema description coverage, the description should explain the two required parameters ('run_id', 'artifact_path'). It does not define what they represent, their formats, or constraints. The description only adds context about file type but not parameter details.

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 verb 'Read and return' and the resource 'artifact content', with a specific file type qualifier 'for text/json files'. This distinguishes it from binary artifacts but not clearly from sibling 'get_run_artifact' which may serve a similar purpose.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_run_artifact' or 'get_run_artifacts'. The description does not mention prerequisites, limitations, or exclusions.

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