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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered by structured data. The description adds the useful fact that the tool has two distinct behaviors (listing versus file retrieval), but says nothing about pagination, result limits, or what happens on a missing path.

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?

A single front-loaded sentence with no filler; the two modes are joined compactly and nothing is repeated from the schema.

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 three-parameter read tool with full annotation coverage and no output schema, this is minimally adequate. It omits what the listing contains and how artefact content is returned, which an agent would want before choosing between the two modes.

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 description coverage is 67% and the key discriminator (relative_path empty lists, non-empty fetches) is already documented in the schema. The description reinforces the task-scoped nature but adds no format, path-syntax, or workspace_id meaning beyond the schema.

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 ("List profile task artefacts") plus a second mode ("fetch artefact file content for a specific task"). An agent can tell what it returns, though the description never distinguishes this tool from near-siblings like get_profile_details or list_profiles.

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 dual-mode behavior hints at when each mode applies, but the actual condition (empty vs non-empty relative_path) is only spelled out in the schema, not the description. There is no explicit when-to-use or when-not-to-use guidance relative to alternatives.

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