list_horizontal_artifacts

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

Given no annotations, the description adds context that these artifacts 'span multiple phases', indicating the scope. No side effects or restrictions are disclosed, but the tool is a simple list with no parameters and likely has output schema.

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 one sentence, front-loads the purpose, and includes just enough detail without redundancy.

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?

With no parameters and an output schema (presumably), the description fully explains the tool's function and distinguishes it from siblings. It is complete for the tool's complexity.

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 input schema has zero parameters, so baseline is 4. The description does not need to add parameter details, and it provides examples of returned artifacts.

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 clearly states the verb 'List' and resource 'horizontal artifacts', specifies they span multiple phases, and provides concrete examples (governance model, RAID log, etc.), distinguishing it from siblings like list_phases or list_deliverables.

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 implies usage for listing cross-phase artifacts and gives examples, but does not explicitly state when to use or not use this tool versus alternatives, nor provide any conditions or exclusions.

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