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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, and the description is consistent with that — it explicitly notes 'It takes no arguments' and pushes all mutation to a human or the full connection. Beyond the annotations it adds genuine context: what the reach field means and how to use it to distinguish an empty result from data that is out of scope. It stops short of describing response shape or error behavior, which keeps it at a 4 rather than a 5.

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 purpose is front-loaded in the first sentence and each subsequent sentence adds a distinct piece of information (scope interpretation, call timing, out-of-scope mutations). The opening sentence is a long comma-chained enumeration of return fields, which is dense but each item is load-bearing, so nothing is wasted.

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?

There is no output schema and no parameters, so the description carries the whole burden of explaining what comes back — and it does, field by field, plus how to interpret the reach value. For a zero-argument read-only introspection tool, an agent has everything needed to call it and use the result.

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 tool takes zero parameters and the description confirms this directly with 'It takes no arguments', matching additionalProperties: false in the schema. With no parameters there is no semantic gap to fill, so the baseline of 4 applies.

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 and resource ('Shows who this neonloops connection acts as') and then enumerates exactly what the answer contains: workspace id, member role, token scopes, capabilities, callable tool names, and reachable non-archived projects with names and ids. No sibling tool does identity/scope introspection, so the distinction is obvious from the text alone.

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?

Gives explicit trigger points: at session start, before automating a task, and again when a list comes back empty. It also names what it does not handle and routes that work elsewhere ('Renaming, archiving or deleting a project is deliberately left to a person, in the app or on the full connection (/api/mcp/full)'), so the agent knows both when to call it and when to stop using this connection.

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