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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds real behavioral context: tokens are never returned, only whether one is set, the caller's own change permission is reported, and the licence confirmation timestamp is included. It omits return ordering, pagination (if any) and the empty-list behavior.

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 content is largely justified because there is no output schema and return shape must be described. However, it is delivered as one sprawling multi-clause sentence, mixing return fields with permission facts and a UI pointer, with no front-loaded summary of the operation itself, which hurts scanability.

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 no output schema, the description does the necessary work of explaining what comes back, down to licence attribution and webhook/token presence. It still lacks ordering, volume and what an empty result means, and offers no pointer to the connect/set tools an agent would likely need next.

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?

There is a single parameter with 100% schema description coverage ('Key of the project, e.g. LIB'), so the schema carries the full burden. The description adds nothing about projectKey or how to obtain it, which is the baseline-3 case rather than a 4.

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 names the specific resource (the GitHub and GitLab repositories a project is connected to) and enumerates the fields returned, so an agent knows exactly what it gets. It never mentions the siblings that mutate this same list (connect_repository, set_repository_open_source), so it is clear but not differentiated from alternatives.

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?

Usage is only implied: 'Any member may read it' tells the agent who is permitted, which is genuinely useful context, but there is no explicit statement of when to call this versus connect_repository or list_code, nor any precondition such as the project needing an existing connection.

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