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

No annotations are provided, so the description must carry the full burden. It states the operation is read-only and requires specific permissions, but it does not disclose idempotency, side effects, or response structure. The vague phrase 'details, files, and file tree' leaves ambiguity about output.

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 consists of two concise sentences: first stating the action and scope, second noting the required permission. No redundant information. Front-loaded with the core purpose.

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 simplicity (1 parameter, no output schema, no annotations), the description covers basic purpose and auth but lacks detail on return structure and usage scenarios, leaving gaps for an agent to fully understand the tool's capabilities.

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 single parameter 'artifactBundleId' has no description in the input schema (0% coverage). The tool description does not explain the parameter's purpose or format beyond the schema. Although the name is self-explanatory, the description adds no value to parameter understanding.

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?

Description clearly states 'read artifact bundle details, files, and file tree', specifying the action and scope. However, it does not differentiate from sibling read tools like rubrkit_read_artifact_file or rubrkit_read_audit, which limits clarity for tool selection.

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 on when to use this tool vs alternatives. The only usage information is the required permission 'artifact_bundles:read'. There is no mention of when not to use it or which sibling tools to consider for different scenarios.

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