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

Although annotations already declare readOnlyHint=true and destructiveHint=false, the description adds substantial behavioral context: newest-first ordering, detailed outcome semantics for checklist and duty rules, and read-access scope ('Any member may read it'). This is far beyond what the annotations provide.

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?

It is front-loaded with the resource and ordering, then efficiently enumerates only the outcome details needed to interpret results. Despite being dense, every clause earns its place by explaining a distinct outcome state.

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 return content, including all outcome values and their meanings. It also states access permissions, making the definition complete for an agent to call and interpret the tool.

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 all parameters (projectKey, id, limit) are fully documented in the schema. The description does not add parameter-specific guidance beyond what the schema already provides, so the baseline score 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 names the specific resource ('A project rule's journal') and its ordering ('newest first'), and explains exactly what each entry represents. It is clearly distinguishable from list_project_rules and update_project_rule.

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?

It gives a clear diagnostic use case ('The place to look when a checklist did not appear or an agent did not take an issue'), which tells an agent when this tool is relevant. It does not explicitly name alternatives or when-not-to-use cases, but the context is strong enough.

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