team_time_list_members

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add protocol detail — and it does, disclosing that responses are paginated into pages with a nextCursor and that the limit must be held constant while following the cursor. It doesn't note whether paging is stable under concurrent changes, but this is meaningful added context beyond the annotations.

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?

Two short sentences, the operation front-loaded and pagination instructions second. Nothing redundant, though the brevity comes partly from under-specification.

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 2-param, no-output-schema, annotated read tool this is roughly adequate — safety is covered by annotations and the cursor protocol is explained. What's missing is scope: what a 'member' is and what the page items contain, which the agent needs to use the results correctly.

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 carry both parameters. It does clarify that 'limit' is the page size which must remain unchanged across pages, and cursor is implied via 'page.nextCursor', but it omits defaults, the maximum of 100, and what a cursor string is bound to.

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 verb 'Read' and resource 'members' are stated, which distinguishes it loosely from list_projects/list_tags/list_tasks by resource name. However, 'members' is never qualified (team? workspace? project members?), so the agent cannot tell precisely what is enumerated or how it differs from get_task_agents.

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 statement of when to call this versus the many sibling list/get tools, and no prerequisites or exclusions. The only guidance is procedural: 'Follow page.nextCursor with the same limit.'

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