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

The description discloses that the submission is personally reviewed by a board-certified physician, may return a checkout URL, and could result in a prescription. This goes beyond the annotations (readOnlyHint=false, openWorldHint=true) by explaining the real-world workflow and side effects. There is no contradiction with annotations.

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 three sentences long, each serving a purpose: what the tool does, what the input should be and what it returns, and what happens after submission. It is front-loaded with the primary action and contains no redundant information.

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?

Given the tool's moderate complexity (3 optional/nested parameters, no output schema), the description covers the essential aspects: purpose, input format, return behavior (feedback or checkout URL), and the human involvement. This provides sufficient context for an agent to select and invoke the tool correctly.

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 describes all three parameters with 100% coverage, so the baseline is 3. The description adds value by specifying that the query must follow the 'Appendix letter structure', which is not in the schema, and by implying that the images and session_token relate to attachment and continuation of a submission. This enriches the parameter understanding beyond the schema.

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'), the resource ('a clinical encounter letter'), and the recipient ('Appendix physician team for review'). This distinguishes it from sibling tools like list_conditions and search_knowledge_base, which are read-oriented.

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 provides clear context for when to use the tool: when you need to submit a clinical encounter for physician review. It specifies the required format (Markdown following Appendix letter structure) and the expected outcome (feedback or checkout URL). It does not explicitly mention alternatives, but the sibling tool names make the differentiation obvious.

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