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

The annotations already indicate readOnlyHint=true, so the description does not need to restate safety. It adds useful behavioral context: what a ruleset is, the two rule levels (must vs should) and their failure semantics, and the fact that rules only run inside workflow runs when attached to a workflow connection. These details go beyond the annotations.

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 front-loads the main purpose in its first clause and then uses subsequent sentences to define rulesets, rule levels, and attachment behavior. It is appropriately sized for a list tool without an output schema, though the domain explanation could be slightly tighter.

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 does the work of explaining the return shape: rulesets contain ordered rules, and attachedTo shows workflows and connections. It also explains the meaning of rule levels. Pagination or ordering of the ruleset list itself is not addressed, but the core contextual needs are covered.

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 input schema has 100% description coverage for its single parameter, projectId. The description does not add any additional syntax, format, or filtering semantics for that parameter, so the schema already carries the full parameter explanation. This meets the baseline of 3 for high schema coverage.

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 opens with a specific verb and resource ('List the project's rulesets') and immediately qualifies the returned content: rules and attachment relationships. It clearly distinguishes this from sibling CRUD tools like create_rulebook or update_rulebook by specifying that this is a read operation listing rulesets with their rules and attachments.

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 explains the domain context of rulesets and when rules execute, but it does not explicitly state when an agent should call this tool versus alternatives such as get_workflow or check_rules. Usage is implied by the list operation, but no direct when-to-use or when-not-to-use guidance is provided.

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