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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no mention of pagination behavior despite limit/offset params, no indication of result ordering or size, and no note that the required 'context' parameter has strict formatting rules.

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 short sentence with zero waste, but it is concise by virtue of omission rather than economy. It is front-loaded with the verb and resource, which is a positive, though there is nothing else to structure.

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 4-parameter paginated list tool with no output schema, the description should at minimum explain pagination, default limits, and what a repository record contains. None of that is present, so an agent must infer call behavior entirely from the schema.

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 only 25% and the sole documented parameter is 'context', which carries its own lengthy instructions in the schema. The description never mentions limit/offset, that results are paginated, or default page size, so it fails to compensate for the undocumented parameters.

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?

States a specific verb+resource ('List repositories') and adds the scope 'for a project', which is more than a bare restatement of the title. However it does nothing to distinguish this from nearby siblings like get_repository, refresh_repository, list_projects, or import_repository, so an agent gets the basic idea but no disambiguation.

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?

There is no when-to-use guidance at all — no statement about when to prefer this over get_repository (single repo) or refresh_repository, and no prerequisites. The only usage signal is the implicit 'for a project', which the schema already conveys via the required project_id.

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