team_time_get_task_agents

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds meaningful behavior: it lists the returned content categories, explains pagination via a cursor for older conversation, and notes that a task claim remains authoritative when another agent does not reply. The cursor name is inconsistent with the schema, but the behavioral disclosure itself is substantive.

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 three sentences and front-loads the returned content list. The final sentence about claim authority is somewhat opaque but still relevant coordination context; overall it is tight and readable.

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?

With no output schema, the description does well to enumerate the returned data categories and pagination behavior. However, it leaves the required taskId unexplained, uses a cursor name that does not match the schema, and gives no routing guidance relative to sibling read tools.

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 explain taskId and beforeId. It does neither: taskId is never described, and the only cursor guidance references 'nextBeforeId', which is not a declared parameter (the schema uses 'beforeId'). This mismatch reduces clarity rather than compensating for the schema gap.

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 uses a clear verb ('Read') and enumerates the linked resources: chats, availability, declared files, checkpoints, and recent task messages. It is understandable as a task-scoped read tool, though it does not explicitly distinguish itself from siblings like team_time_get_task or team_time_agent_inbox.

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?

Usage is implied by the listed content and the cursor instruction for older conversation, but there is no explicit guidance on when to choose this tool over team_time_get_task, team_time_agent_inbox, or team_time_get_agent_message. No exclusions or alternatives are named.

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