继续新增就诊人流程

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

No annotations provided. Description lists actions but does not disclose behavioral details such as side effects, required permissions, or what happens on submit. Minimal disclosure beyond what the schema implies.

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?

One sentence listing multiple actions. While concise, it lacks structure and could benefit from separating the use cases or adding bullet points.

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?

With 4 parameters, no output schema, and no annotations, the description is insufficient. Missing context about the multi-step flow, return value, and error conditions.

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 0%. Description mentions parameters (field, value, action, flowId) but does not explain their formats, valid values, or how they relate. For example, 'field' is unclear; 'value' is any type. Does not compensate for schema gaps.

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?

Description states the tool provides a field or performs actions (get captcha, send SMS, submit) for the new patient flow. Clear verb+resource but does not differentiate from sibling tools like patient_add_start or register_*.

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 on when to use this tool vs alternatives. The description does not state prerequisites, flow context, or when to choose specific actions.

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