cuemap_project_artifacts

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

With no annotations provided, the description carries the burden of behavioral disclosure and it explicitly states that the operation does not reload or mutate the project. It does not explain what 'artifact metadata' contains or what side effects may still occur, but the core safety property of this inspection tool is clearly 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 a single sentence that leads with the key verb and object, then adds the critical non-mutation qualifier. There is no redundant phrasing or filler.

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?

The tool has only one optional parameter, and that parameter is documented in the schema. However, with no output schema and no annotations, the description leaves 'CueBridge artifact metadata' vague and does not state what the returned metadata includes or whether the project must already be loaded. That is a meaningful gap for an agent choosing or invoking the tool.

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 100%: the only parameter 'project' is fully described as an optional ID defaulting to the repository-scoped project. The tool description adds no new parameter-level meaning, so the baseline score of 3 applies.

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 uses a specific verb ('Inspect') and a clear resource ('CueBridge artifact metadata for a CueMap project'), and adds a non-reloading/non-mutating qualifier that separates it from mutation-oriented siblings like cuemap_project_save, cuemap_project_push, and cuemap_project_sync. This is enough for an agent to know what the tool does at a glance.

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 phrase 'without reloading or mutating it' implies this is the read-only metadata inspection option, but no explicit when-to-use guidance or alternative is named. Sibling names suggest related operations, yet the description does not tell an agent when to choose this over cuemap_project_pack, cuemap_project_export, or cuemap_lexicon_inspect.

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