listAppointmentOutcomes

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

With no annotations present, the description carries the full burden of behavioral disclosure, but it only states a basic action. It omits any mention of read-only safety, pagination, ordering, authentication requirements, or return shape. The phrase adds no behavioral detail beyond what the tool name already 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?

The description is extremely concise and front-loaded, using only three words. Every word contributes to clarity, but it is so terse that it lacks any additional contextual structure (e.g., examples or related tool references) that could help the agent. Still, it is appropriately sized for a tool with no parameters and a straightforward action.

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?

Description completeness is low. While the tool is simple (zero params, no output schema), the description provides no details about what an appointment outcome is, whether results are paginated, or what the response format looks like. It fails to give agents enough context to confidently invoke the tool, especially given the lack of annotations.

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 tool has zero parameters and the schema coverage is 100%, so the baseline is 4. There is no parameter information needed, and the description doesn't need to compensate for any undocumented fields, as there are none.

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 'List appointment outcomes' uses a specific verb ('List') and resource ('appointment outcomes'), clearly distinguishing it from siblings like listAppointments, listAppointmentTypes, getAppointmentOutcome, and updateAppointmentOutcome. Even though it mirrors the tool name, it expands the camel case into a readable phrase, which is 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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention that this is the collection-list version of getAppointmentOutcome, nor does it explain any filtering, pagination, or contextual triggers. An agent is left to infer usage purely from the name.

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