get_deliverable

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

No annotations provided, and description only lists what the tool returns without disclosing behavioral aspects such as idempotency, read-only nature, or error handling. Relies on output schema but does not explain 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?

Description is a single sentence that clearly front-loads the purpose ('Full spec for a single deliverable') and lists contents concisely, though separating into two sentences could improve readability.

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 description tells what the tool returns but lacks context about the required slug parameter and does not differentiate usage from siblings. Output schema exists, but parameter info is absent.

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 single parameter 'slug' has no description in schema or tool description. The description does not clarify its meaning beyond what the name implies, providing no added value for parameter understanding.

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?

Description clearly states the tool retrieves the full specification for a single deliverable, listing specific components (purpose, audience, inputs, etc.), which distinguishes it from sibling tools like list_deliverables or get_dependencies.

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?

Description implies usage for obtaining comprehensive details about one deliverable, but does not explicitly state when to use this vs. alternatives like list_deliverables for overviews or get_dependencies for graph dependencies.

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