Submit Document

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

With no annotations provided, the description carries the full burden. It does disclose the core behavior: a state transition from Draft to Submitted, and the submittable DocType constraint. However, it omits other relevant behavioral traits such as what happens on failure, return values, or whether the action is reversible, which is significant for a mutation tool.

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 sentence that front-loads the action and includes a critical constraint. Every word is necessary, with no redundant or filler content.

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 has only two simple parameters and no output schema. The description covers the purpose and a key constraint, but it does not explain what the tool returns or error scenarios. An agent might need to know how to confirm success, making the description adequate but incomplete in some aspects.

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 provides 100% coverage for both parameters (name and doctype) with descriptions. The tool description adds no extra parameter-level meaning, so it does not improve upon the schema. The baseline of 3 applies given high schema coverage.

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 'Submit a document' and specifies the exact state transition 'Draft → Submitted'. It also notes the constraint 'Only works for submittable DocTypes,' which distinguishes it from siblings like create_document, update_document, and cancel_document. This makes the tool's purpose unambiguous.

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 when to use the tool: to submit a document, moving it from Draft to Submitted. It also provides a clear constraint (only submittable DocTypes). However, it does not explicitly name alternatives or state when not to use it, though the purpose is specific enough to guide selection.

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