timetree_get_calendar_members

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

No annotations are provided, so the description carries the full behavioral burden. It clearly indicates a read operation and discloses the deactivated-member filtering option, which is useful. However, it does not mention auth requirements, default exclusion behavior, or response contents, leaving some behavioral ambiguity.

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 a single, concise sentence that front-loads the key action and resource, then adds the optional behavior. No wasted words or redundant details.

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 tool with 2 parameters, no annotations, and no output schema, the description gives minimal but sufficient context for the primary action. It lacks details about required authentication, what fields each member includes (e.g., name, email, role), and error behavior, but the core call is understandable. It is adequate but not complete for a production agent.

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%, so the description must compensate. It adds meaning for include_deactivated ('optionally including deactivated members') and implies the core resource for calendar_id, but it does not explain the calendar_id format (string vs integer). It still adds meaningful semantic value beyond the schema.

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 states a specific verb ('Read'), a clear resource ('active members of a TimeTree calendar'), and a distinguishing optional behavior ('including deactivated members'). It clearly separates this tool from siblings like timetree_get_calendar_virtual_members and timetree_list_calendars.

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 when to use the tool (reading calendar members) but does not explicitly contrast it with alternatives such as timetree_get_calendar_virtual_members or provide exclusions. The optional 'including deactivated members' hints at a usage toggle, but no explicit when-to-use guidance is given.

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