get_draft

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Retrieve' implies a read-only operation, but the description does not state whether the result is the full draft, what happens for missing IDs, or whether any side effects or permissions are involved. This is minimal coverage for a tool with no annotation safety hints.

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, well-formed sentence with no redundant words. It front-loads the core action and object, making it easy for an agent to scan and understand quickly.

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?

For a simple one-parameter retrieval tool, the description is minimally viable: the agent knows the action, the resource, and the existence condition. However, with no output schema and no annotations, it leaves room for ambiguity about the return payload and does not help an agent choose this tool over related read-oriented siblings.

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 has a single required 'id' parameter with zero description coverage, and the tool description does not explicitly explain what 'id' refers to beyond the inferred draft ID. The only added semantic is that the draft must be 'existing,' which is too thin to compensate for the missing parameter documentation.

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 'Retrieve' and names the resource, an existing unpublished deposition draft. This clearly distinguishes it from create_draft, update_draft, and publish_draft, though it does not explicitly contrast it with deposition_status or other read-adjacent siblings.

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 given about when to use this tool versus siblings like validate_deposition, publication_review, or deposition_status. The phrase 'existing unpublished' hints at when the draft is retrievable, but there is no explicit when-to-use or when-not-to-use instruction.

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