List Eden Diagnostic Artifacts

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

Annotations already declare readOnlyHint and idempotentHint, so the agent knows it is a safe read operation. The description adds the scope of the listing (only Eden MCP artifacts) and the inclusion of size information, which provides context beyond what annotations offer.

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 is front-loaded with the action and includes all necessary scope details without any redundant text or fluff.

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 is simple and has an output schema, so return values are handled elsewhere. However, the description is minimal and does not explain the purpose or effect of the session_id parameter, and it vaguely refers to 'diagnostic artifacts' without further detail, leaving some gaps for a complete understanding.

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 schema includes one parameter (session_id) with no description and 0% schema description coverage. The description does not mention session_id at all, failing to compensate for the lack of parameter documentation, leaving the agent without guidance on how to use the parameter.

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 the specific verb 'List' and clearly identifies the resource as 'diagnostic artifacts generated by Eden MCP' while also noting size detail. This distinguishes it from sibling tools like eden_export_diagnostics and eden_cleanup_artifacts.

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 description provides clear context that this tool lists artifacts only from Eden MCP, implying when it would be used. However, it does not explicitly mention when to use this tool over alternatives like eden_export_diagnostics or eden_cleanup_artifacts, nor does it state exclusions.

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