patient_op_schedule

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

Without annotations, the description carries the burden; it clearly indicates this is a read/query operation, defines the time scope (future), and lists the exact return fields. It does not mention potential edge cases or permission requirements beyond the implied credentials.

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 concise, front-loaded with the main purpose, then provides usage guidance in the second sentence, and ends with a clear list of return fields.

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 simple with 3 required params and no output schema. The description covers purpose, scope, and return fields, and distinguishes the sibling tool. However, it fails to describe the parameters, which are essential for invocation, especially given zero schema descriptions.

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%. The description does not explain the meaning of hisno, eip_id, or eip_password, leaving the agent to infer from context. Some minimal implication exists (hisno is likely the patient identifier), but no explicit details are provided.

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 tool retrieves a patient's scheduled surgery list and specifies it queries future scheduled procedures, differentiating from sibling tool patient_op_list for past records.

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?

Explicitly instructs to use patient_op_list for past completed surgeries, providing a clear alternative and exclusion criteria.

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