list_default_reviewer_conditions

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds minimal behavioral context beyond stating the purpose ('automatically added as reviewers'). It doesn't disclose any other behaviors (e.g., pagination, sorting, or error cases), but for a simple read-only list this is acceptable.

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 very concise: two sentences with no wasted words. It front-loads the action and resource, immediately followed by a clarifying sentence about the purpose. It earns its place.

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?

Given the tool's simplicity (no output schema, only 3 parameters with full coverage), the description is complete enough for an agent to understand what it does. It could optionally mention the return format or pagination behavior, but that's not required for core functionality.

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%, so the parameters are already documented. The description does not add any extra meaning or usage guidance for the parameters beyond what the schema provides. Baseline 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 clearly states the action (list) and the resource (default reviewer conditions for a repository) with enough context about what these conditions do (automatically add reviewers to PRs). It distinguishes from siblings like list_reviewer_groups and list_branch_restrictions by specifying a unique resource, though it doesn't explicitly differentiate.

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 implies when to use the tool (to view conditions that auto-add reviewers), but it doesn't provide explicit guidance on when not to use it or mention alternatives among the many sibling list tools. The context is clear enough for an agent to infer usage based on the resource name.

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