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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds meaningful context by stating the required VIEW access level, API-key scope, and the full returned settings shape. It stops short of covering error behavior or rate limits, so 4 is appropriate.

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-loads the core read action and then spends the remaining words on return fields, which is justified because no output schema exists. The long field enumeration is necessary rather than repetitive, though the response remains a single dense paragraph.

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 fully explains the returned TaskSharingSettingsDTO fields and the access/scope requirements an agent needs. The input schema is complete and annotations cover safety, so no critical context is missing for correct invocation.

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 coverage is 100%, with all three parameters documented directly in the schema, so the baseline is 3. The description adds no input-parameter formatting or selection guidance beyond what the schema already 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?

States a specific verb ('Read') and resource ('task's current public sharing settings'), and the detailed DTO return list makes the operation unambiguous. It does not explicitly name or contrast with the write sibling pm_configure_task_sharing, so it falls short of a 5.

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?

Provides an access prerequisite ('Requires at least VIEW access') and API-key scope ('tasks:read'), which tells the agent when the call is permitted. However, it never explicitly says when to use this instead of pm_configure_task_sharing or another alternative, leaving the read-vs-configure distinction implicit.

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