read_artifact_group

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

With no annotations, the description carries the burden of behavioral disclosure. It conveys a read-only operation and indicates the return includes full file set and metadata, but it does not address error behavior, permissions, or any side effects. This is minimal but not misleading, meriting an average score.

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, front-loaded sentence that efficiently states the action, scope, and a use case without any wasted words. Every word earns its place, and it is perfectly concise.

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 simple read tool with one parameter and an output schema, the description is complete enough. It clarifies the scope ('full file set and metadata') and provides a practical workflow hint. It could mention error cases or read-only nature explicitly, but the context signals and schema compensate, warranting a 4.

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 input schema already has 100% coverage with a detailed description of the 'ref' parameter, so the baseline is 3. The tool description adds no additional parameter semantics beyond what the schema provides, staying at that baseline.

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 reads an artifact group's full file set and metadata, using the specific verb 'read' and resource 'artifact group'. It also distinguishes from siblings by mentioning the context of iterating before calling edit_artifact_group_item, making its purpose unmistakable.

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 gives clear usage context by stating 'so you can iterate on it (e.g. before calling edit_artifact_group_item)', implying when to use this tool. However, it does not explicitly exclude alternatives or mention when not to use it, so it falls short of a 5.

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