hero_list_appointments

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful trait — fields are auto-selected from the HERO schema, implying a variable return shape — but says nothing about rate limits, page sizes, or result counts for a tool explicitly designed around paging.

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 short sentences, front-loaded with the action and resource, then constraints. No filler, though the schema pointer is repeated from the schema description itself.

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?

A read-only list tool with full schema coverage and no output schema; the note that fields are auto-selected from the HERO schema partially compensates for the missing return definition. Pagination and filtering behaviors are adequately covered for correct invocation.

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 coverage is 100%, so all three parameters are documented in the schema itself (including the instruction to call hero_schema first). The description restates the `filters` behavior already present in the schema rather than adding new syntax or format detail, so baseline 3 applies.

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?

States a specific verb (List) and resource (calendar events/appointments from HERO), naming the native term 'Termine' for disambiguation. It is clearly separable from siblings like hero_list_customers or hero_list_documents by resource, though it makes no explicit contrast statement.

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?

Gives concrete guidance on how to filter ('Pass date filters via `filters`') and points to hero_schema, which implies the right usage context. It does not say when this tool is preferable to hero_graphql or how results relate to other hero_list_* calls.

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