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

The description adds the return fields, which is useful. However, it falsely claims 'Filter by status and labels' while the schema has a 'state' parameter and no 'labels' parameter. This misleading claim contradicts the schema and could cause the agent to pass an invalid 'labels' argument. Annotations already cover read-only and idempotent traits, so the description's misleading filter is a significant transparency issue.

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?

Two sentences, front-loaded with purpose and return fields. The structure is efficient and easy to parse, though the content includes the 'labels' inaccuracy. The compactness is good.

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 an output schema and strong annotations, the description doesn't need to explain return formats. It is adequate for a simple list tool, but the erroneous 'labels' filter and use of 'status' instead of 'state' create a gap in completeness, leaving the agent uncertain about actual filter options.

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 baseline is 3. The description adds minimal semantic value beyond the schema: it mentions 'project ID' (already required) and repeats filter capabilities, though 'labels' is not a schema parameter. No additional parameter nuances are provided.

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 tool searches issues in a GitLab project by project ID and lists the returned fields (ID, title, state, labels, assignee, URL). This distinguishes it from sibling tools like gitlab_list_mrs (merge requests) and gitlab_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?

It provides clear context: search issues by project ID and filter by status/labels. However, it does not explicitly mention when not to use it or name alternatives, though the context is sufficient for an agent to select this tool for issue listing.

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