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

With no annotations, the description carries the full burden, and it delivers: it discloses read-only journal semantics, newest-first ordering, the full set of outcome values with meanings ('applied', 'alreadyThere', 'tooLong', duty outcomes), and access control ('Any member may read it').

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 text is dense but every clause earns its place: the outcome enumerations are essential given the absence of an output schema, and the final guidance/access sentences add distinct value. The core purpose is front-loaded.

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?

For a tool with no output schema and no annotations, the description fully compensates: it defines the entry content, all possible outcomes and their consequences, ordering, and who may read it. An agent can predict the returned data without further lookup.

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 description coverage is 100%, so the schema already documents projectKey, id, and limit. The description adds no parameter-specific meaning beyond the schema, so 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 opens with 'A project rule's journal, newest first,' immediately identifying the specific resource and operation. It details what each entry records (which issue, who moved it, outcome) and enumerates the outcome vocabulary, making the tool's function unmistakable and distinct from siblings like 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 an explicit diagnostic use case: 'The place to look when a checklist did not appear or an agent did not take an issue.' It does not name sibling alternatives or state when not to use it, but the context is clear enough for selection.

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