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

The description reveals observable behavior beyond what annotations state: creating a new list linked into the parent's thread, pinging the org, and showing the thread in both the worker portal and Simple Mode. It also explains the two-way nature of the tasking flow. While annotations already indicate this is not read-only, the description adds meaningful context about side effects (org ping, portal visibility) that directly informs an agent's expectations.

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 compact but information-dense. The opening line communicates the core purpose in one sentence, and the rest adds genuine value (examples, response_type hints, follow-up guidance). It avoids redundant phrases and every sentence earns its place, though it could arguably be trimmed slightly without losing meaning.

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 list-reply tool with a solid schema (100% coverage, required params clearly stated) and no output schema, the description fully covers what an agent needs: the purpose, the workflow context, examples of response types, and the follow-up tools to read answers. Nothing critical is missing for an agent to select and invoke this tool 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?

The schema has 100% description coverage, so parameters are already well-documented. The description adds extra context on top by explaining response_type values in the schema (e.g., 'date' for scheduling windows, 'text' for info requests), which reinforces selection. It also frames parent_list_id and title with concrete examples beyond what the schema provides.

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 identifies this as a two-way tasking primitive that replies to a task list with a new list linked into the parent's thread. It gives concrete examples of use cases (e.g., 'Grant access — pick a window' with response_type date) and distinguishes the tool's responsive nature. The verb 'Reply to' is specific and immediately tells an agent this is for responding to an existing task list, not creating a standalone one.

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 explicitly frames this as the two-way tasking primitive and explains when to use it: to reply to a task list with a new list aimed back at the sender. It also provides follow-up guidance, telling agents to use tascan_get_thread-style follow-up via tascan_list_projects/tascan_get_report to read answers. This is a clear usage scenario with a pointer to related tools for the next step.

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