Get draft post

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

No annotations are provided, so the description carries the full burden. 'Fetch' implies a read operation, but it does not state whether the tool modifies anything, what it returns, or behavior on missing ids. Important behavioral traits like 'does not modify' or 'returns the draft object' are left implicit.

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 extremely brief and front-loaded, containing only one sentence with no filler. The word 'single' adds slight redundancy with 'by id' but does not harm clarity. It is concise and effective for the simple operation.

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 tool is a simple get-by-id operation with one parameter, so the description is relatively adequate. However, without an output schema or annotations, it does not explain what is returned or how errors are handled. It is not fully complete but serves as a minimal viable description.

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% and the 'id' parameter is described as 'Draft id.' The description adds 'by id' which reinforces but does not go beyond the schema. No additional meaning is provided beyond what the schema already documents, so the baseline score of 3 applies.

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 action ('Fetch') and resource ('a single draft by id'), distinguishing it from sibling tools like list_drafts (plural) and update_draft (mutation). The tool name and title align, and the scope is explicit.

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 implicitly guides use for retrieving one specific draft by id, but it does not explicitly mention when not to use it or mention alternatives like list_drafts for multiple drafts. The single-by-id phrasing suggests the use case, but no exclusions or alternative comparisons are provided.

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