search_appointments

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

With no annotations provided, the description carries the full burden. It discloses that the tool is read-only (tier: readonly-owner) and returns IDs, which is useful. However, it doesn't explain behaviors like pagination, response structure, or what happens with no filters, leaving gaps for a 12-parameter tool.

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, with two sentences (or one sentence plus a bracket) that front-load the core purpose. It includes the endpoint and tier with no fluff, every element earns its place.

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 description is too minimal for a tool with 12 parameters and no output schema. It doesn't explain the return format (e.g., array of IDs), how filters combine, or suggest next steps like fetching full data with get_appointments. Leaves the agent with many unanswered questions.

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 only 8% (only status has a description). The description itself doesn't explain any of the 12 parameters, including cryptic ones like includeData and extra_filters. The agent gets almost no guidance on parameter meaning beyond vague names.

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 searches for appointments and returns matching IDs, with a specific verb and resource. It distinguishes from get_appointments by highlighting that it returns only IDs, making the purpose 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?

The description implies usage as a search tool that returns IDs, but it does not explicitly state when to use this tool versus alternatives like get_appointments. The 'return matching IDs' hint suggests a follow-up fetch, but no direct guidance is provided.

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