inventory_mcdev_project_artifacts

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

With no annotations, the description carries the full burden and does well: it discloses read-only/metadata-only behavior, no remote-freshness guarantee, no atomic sandbox, and warns to prevent concurrent filesystem mutation. Missing only error/failure behavior (e.g. what happens if workspaceRoot is absent or paths are unconfigured).

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?

Two dense sentences, front-loaded with the capability and followed by limits, with no filler. The second sentence compresses several distinct caveats into one run-on clause, which slightly hurts scanability but wastes nothing.

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 read-only inventory with no output schema, the description covers scope and behavioral caveats adequately, but leaves the agent guessing about the shape of the returned inventory and about what maxDepth/maxEntries actually control. Adequate, not complete.

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 33% – only workspaceRoot is documented. The description adds nothing about maxDepth or maxEntries, both of which have non-obvious bounds (1-12, 1-10000) and unclear interaction with the walk. With low coverage the description should compensate but instead ignores two of three parameters.

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: 'read-only, metadata-only inventory of configured retrieve/deploy paths.' It also draws a boundary against content-reading siblings by saying it 'does not open artifact contents', which separates it from read_mcdev_artifact_source and resolve_mcdev_project_artifact. It stops short of naming those alternatives 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 'does not / never' clauses (no contents, no dependency confirmation, no auth, no logs) give clear negative guardrails, so an agent knows what this tool will not answer. However there is no positive statement of when to reach for it versus resolve_mcdev_project_artifact or read_mcdev_artifact_source.

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