List Prismism Artifacts

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

With no annotations provided, the description carries the full burden. It discloses pagination behavior and user-scoping ('your'), but omits critical operational details such as read-only status, rate limits, sorting order, or response structure.

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?

Extremely efficient single sentence with zero waste. Front-loaded with the action ('List') and immediately qualifies the resource and mechanism. Every word earns its place.

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?

Given the simple 2-parameter schema with full coverage, the description is minimally adequate. However, with no output schema and no annotations to declare safety properties, the description should ideally disclose more about return values or read-only status to be 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 coverage is 100% with clear descriptions for 'page' and 'limit'. The description mentions 'pagination' which loosely maps to these parameters, but adds no specific semantic guidance beyond what the schema already provides. Baseline 3 is appropriate given high schema coverage.

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?

Uses specific verb 'List' with clear resource 'published artifacts' and scope 'your'. Mention of 'pagination' implicitly distinguishes from sibling 'prismism_get' (single retrieval), though it doesn't explicitly state when to use which.

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?

Provides no explicit guidance on when to use this tool versus siblings like 'prismism_get' or 'prismism_publish'. No mention of prerequisites or conditions that would trigger selection of this tool over alternatives.

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