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

With no annotations provided, the description carries the behavioral disclosure burden. It states the operation returns a 'paginated list' and specifies the kind of content (names, projections, base map references), which conveys a read-only, non-mutating behavior. It does not explicitly mention lack of side effects, but 'List' inherently implies a safe read operation.

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 two sentences long and front-loaded with the primary verb and resource. Every sentence adds value: the first states the core function, the second details the return payload. No filler or repetition.

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 straightforward list operation with a full input schema and an output schema present, the description sufficiently covers purpose, scope, pagination, and return content. There are no obvious gaps, and the description is complete for an agent to decide when to invoke it.

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 schema already describes both parameters (page, page_size) with defaults and limits, achieving 100% coverage. The description adds no additional parameter-specific semantics beyond the general 'paginated list' phrase, so the baseline 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 clearly states the verb 'List' and the resource 'ANUGA simulation projects' with a scoping qualifier ('accessible to the authenticated user'). It also mentions the returned data fields, which distinguishes it from sibling tools like list_runs and get_project.

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 provides clear context on what the tool does and its scope ('accessible to the authenticated user'), but it does not explicitly state when to use it over alternatives such as get_project. For a simple list tool, the use case is evident, but there is no explicit exclusion or alternative comparison.

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