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

Annotations already establish read-only, idempotent and safe, and the description layers meaningful domain behavior on top: task-level values win over list values, the floor rule for Decisions lists and passkey cards, and the inherited agent_assignee. The one gap is that it never says what happens when neither or both ids are supplied.

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?

Front-loaded with verb and resource, but the single sentence is overloaded with stacked parentheticals and domain jargon, making it hard to scan. The information is relevant but poorly staged.

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?

There is no output schema, and the description steps in to enumerate the returned fields (access_level, effective level, human assignees, agent_assignee, floor), which is exactly what's needed. Missing only the edge-case behavior when zero or two identifiers are supplied.

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 parameter meaning; it does identify list_id as a task list and task_id as a task and explains inheritance. It does not state whether the two are required, mutually exclusive, or which takes precedence when both are passed (the 'task-level wins' line describes the data model, not the parameters).

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?

States a specific verb (Read) and resource (the access object) and scopes it to either a task list (list_id) or a task (task_id). The list-vs-task distinction is genuine disambiguation, though it never names the write counterpart tascan_set_access to complete the picture.

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 only implied: pass list_id to read a list's access or task_id to read a task's. There is no 'use this when…' framing, no mention that reads of access should go here while changes go to tascan_set_access, and no exclusions.

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