list_deliverables

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states the basic purpose and defines deliverables; it fails to mention important traits like read-only nature, pagination, authentication requirements, or whether results are filtered by default. This is insufficient for an agent to fully understand the tool's behavior.

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 consists of two concise sentences. The first sentence states the core purpose, and the second adds valuable context about deliverables. It is front-loaded and efficient, though a more structured format (e.g., listing constraints or parameters) could improve usability.

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 tool's low parameter count and existence of an output schema, the description provides a minimal but acceptable overview. However, it lacks usage guidelines and parameter semantics, which are necessary for confident use. The description is adequate for an agent familiar with the domain but incomplete for a new agent.

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 0%, and the description provides no explanation or examples for the two parameters (primary_phase and layer). The agent cannot infer what these parameters control or their formats, making the tool difficult to invoke correctly.

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 tool lists deliverables from a phase-by-phase taxonomy (Layer 3-5 nodes) and defines deliverables as formatted artifacts. This is specific and informative, but it does not differentiate from sibling tools like list_analyses or get_deliverable.

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?

No guidance is provided on when to use this tool versus alternatives. The description omits any conditions, prerequisites, or hints about when to prefer list_deliverables over related tools such as get_deliverable or list_analyses.

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