get_task_members

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It doesn't mention whether members differ from watchers, whether the response includes role/permission info, pagination behavior, or anything about the return structure. For a read-only retrieval tool with zero annotation coverage, this is a minimal disclosure.

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?

One sentence, zero waste. It's appropriately minimal for a simple retrieval tool. Nothing extraneous.

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 tool is simple (1 param, no output schema, no nested objects), and the description adequately conveys the primary purpose. However, without annotations, it doesn't provide additional context like access control requirements or whether members differ from watchers, which given the sibling tool set would be useful.

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?

The single parameter task_id is fully described in the schema (100% coverage) as 'The task ID'. The description adds no further semantic meaning beyond what the schema already provides, so the 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?

The description 'Get all members of a task' clearly states the verb (get) and resource (task members). It's distinguishable from siblings like get_task_watchers and get_space_members since it specifically targets task members, though it doesn't explicitly differentiate from these related member/watcher queries.

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?

No guidance on when to use this vs. alternatives like get_task_watchers or get_list_members. The description doesn't clarify the distinction between task members and task watchers, which a user might confuse given the sibling tool names.

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