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

Annotations already declare read-only, non-destructive, and closed-world behavior. The description reinforces this and adds useful context that activity is bounded and raw provider payloads are not exposed, though it does not discuss permissions or detailed response shape.

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 focused sentences with no wasted text. The usage condition is front-loaded and the read-only return behavior follows immediately.

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?

Given the read-only annotations and fully described schema, the description is nearly complete. It explains what is returned at a high level and notes the bounded activity/raw-payload constraint, though it could say more about link fields or response structure since no output schema exists.

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 100%, so the schema already documents space_id, activity_limit, and include_activity thoroughly. The description adds a little context about bounded sync activity, but parameter meaning is primarily carried by the schema, making 3 the appropriate baseline.

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 a specific verb and resource: listing repository links for a Space. It also frames the purpose around Autopilot, repo sync, suggestion generation, trigger events, and sync activity, though it does not explicitly contrast itself with sibling tools like update-space-repository-link or delete-space-repository-link.

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 gives clear when-to-use scenarios: when the user asks which repositories are linked to a Space for Autopilot, repo sync, suggestions, triggers, or recent activity. It stops short of naming exclusions or alternatives, but the intended context is explicit.

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