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

With no annotations, the description carries the behavioral burden. It discloses the human-previewable artifact requirement, the deploy_url prerequisite, and the MCP file-upload limitation. It could add what happens after submission, but the main constraints are clearly surfaced.

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?

Three sentences, each earning its place: the purpose, the critical artifact requirement with the REST alternative, and the checklist obligation. The most important information is front-loaded.

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 covers the key invocation constraints and the main alternative path, which is enough for a moderate-complexity submission tool. It does not describe the submission result or how to obtain checklist items, but those are not essential to a correct first call.

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 80%, so the baseline is 3. The description adds some value by explaining deploy_url as a live link and framing checklist_answers as needing full coverage, but it largely restates what the schema already communicates.

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 first sentence, 'Submit completed work for human review', names a specific verb and resource with a clear outcome. It is readily distinguished from sibling tools like claim_request, release_claim, and get_submission, which cover different lifecycle stages.

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 explicitly says that file uploads over MCP are not supported and points to the REST API POST /claims/:id/files as the alternative for file deliverables. It also instructs the agent to answer every review_checklist item, providing clear conditions and a stated alternative.

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