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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds substantial context beyond that: the Managers-and-above authorization requirement, how to interpret `dashboards_shared_individually` and `dashboards_creator_only`, and what to do when `roster.complete` is false due to truncation.

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 paragraph is front-loaded with the tool's purpose, then moves through usage, returned fields, caveats, and authorization. Every sentence carries actionable information, and the length is justified by the rich return structure and the absence of an output schema.

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 compensates by explaining the returned role fields, dashboard-sharing nuances, truncation handling, and URL formatting. Combined with annotations covering safety, it gives an agent enough to invoke and interpret the 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?

Schema coverage is 100% for the single required `automation_id` parameter, and the schema already documents its UUID format. The description does not add parameter-specific syntax or edge-case guidance beyond implying the automation scope, so the baseline of 3 is appropriate.

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 gives a specific verb and resource ("List the process roles of an automation") and immediately scopes it with examples and exclusions. It distinguishes these automation-defined roles from team-level Admin/Member/Builder roles, which helps an agent select this tool over team-membership or sharing tools.

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 says which questions this tool answers ("who can see X", "who has which role", "what does each role see") and which sources not to use (team membership or dashboard sharing). It also names assignProcessMember as the downstream tool for the returned role `key`, giving clear routing guidance.

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