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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered by structured data. The description adds genuine value by naming the specific field types returned (project IDs, wiki access flags, work package type IDs), which helps an agent plan downstream calls that consume those IDs.

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?

A single front-loaded sentence with no filler; the most actionable part ('Start here') leads and the payoff (which IDs you get) follows immediately. Every clause 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?

For a zero-parameter listing tool with an output schema, the description covers the calling context adequately and needn't explain return values. It is only slightly thin in that it doesn't indicate scope or whether results are paginated or filtered, but the output schema can carry that detail.

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 tool takes zero parameters, so per the rubric the baseline is 4. There is no parameter surface for the description to explain, and nothing is missing on this dimension.

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 effectively conveys what the tool yields (project IDs, enabled wiki access, work package type IDs) and frames it as the entry point, which distinguishes it from the sibling create/get/list tools that operate on specific projects. However, it never states the action verb 'list' and relies on the reader to infer that it enumerates all projects rather than fetching one.

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?

"Start here" is an explicit sequencing instruction telling the agent to call this before other OpenProject tools, which is strong contextual guidance. It stops short of naming alternatives or exclusions, so it earns a 4 rather than a 5, but the intended call-order is unambiguous.

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