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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description owes less on safety. It usefully adds the role-based access rule and signals the response includes the complete file index, but says nothing about pagination, response size, or failure behavior for artifacts the caller isn't a member of.

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?

One sentence, front-loaded with the verb and return contents, with the access constraint trailing as a qualifier. Nothing is wasted or buried.

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 one-parameter read with no output schema, the description covers purpose, access, and rough return contents. It still leaves gaps on identifier format and on what happens when the artifact isn't accessible, which matter because no output schema exists to explain results.

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 0% for the single id parameter, so the description must carry the load. It clarifies that the id must reference an artifact the caller owns or joined, which adds real meaning, but leaves the identifier format (UUID vs slug) and error conditions undocumented.

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 (Get) and resource (artifact), and specifies exactly what comes back: metadata plus the complete file index. Scope is limited to a single artifact, which implicitly separates it from list_artifacts, but it never names that sibling explicitly.

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 access precondition ('you own or have joined, any role can read') tells the agent when the call will succeed, but there is no explicit guidance on when to choose this over list_artifacts, read_file, or get_skill. Usage is implied rather than directed.

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