notion_get_appointments

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context by stating that results are returned as a JSON string and includes linked Google Calendar event IDs only when synced, which helps set expectations beyond the schema.

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 core query behavior, and structured with clear Args/Returns sections. Some wording is redundant with the schema's property descriptions, but the overall structure remains efficient and scannable.

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?

For a read-only filtered query tool with annotations and an output schema, the description covers the essential aspects: what is queried, which filters exist, what fields are returned, and the return format. It does not mention sorting or pagination, but those are not critical for this simple query tool.

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 reported as 0%, so the description carries the burden of explaining parameters. The Args block successfully documents all four filters and their allowed values, adding practical meaning even though the schema itself also contains property descriptions.

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 a specific verb and resource: 'Query the Notion Appointments database' with optional filters. It also enumerates the returned fields, making the tool's function concrete and distinguishable from sibling calendar/task tools.

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 gives clear context: use this to query appointments with optional date, type, and status filters. It does not explicitly mention when not to use it or point to alternatives like notion_get_appointment_by_gcal_id, but the filter-based framing is understandable enough for tool selection.

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