timetree_get_calendar_virtual_members

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly says 'Read', which indicates a non-mutating operation, and mentions the optional deactivated member inclusion, but it does not disclose the return format, authentication requirements, error cases, or any other behavioral characteristics that would help an agent predict the tool's effects.

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, front-loaded sentence with no filler. It efficiently captures the core action, the object, and the key parameter behavior without redundancy.

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 simple read operation with two parameters, this is a minimal but adequate definition: an agent can infer the primary action and the optional flag. However, there is no output schema and no mention of what the tool returns, and with sparse annotations the description could be strengthened by stating the expected result or clarifying the difference from the non-virtual members 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 0%, so the description must compensate. It does clarify semantically that 'include_deactivated' relates to optionally including deactivated members, but it does not explain the calendar_id parameter's meaning or format beyond the phrase 'a TimeTree calendar'. Given two parameters at zero schema coverage, this leaves one param entirely implicit.

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 ('Read') and resource ('virtual members of a TimeTree calendar'), and the qualifier 'virtual' distinguishes this from sibling tool timetree_get_calendar_members. It also mentions the optional deactivated filter, making the tool's scope unmistakable.

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?

While the description conveys what the tool does, it provides no explicit guidance about when to use this tool versus alternatives such as timetree_get_calendar_members or the broader calendar tools. The only implicit usage signal is the phrase 'Read,' but there is no stated condition or exclusion for when this tool should be selected.

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