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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Read only' in the description is largely redundant. The genuinely additive detail is that each result carries whether the connection can write to that organisation, which tells the agent something about the payload beyond the safety flags, but nothing about volume or ordering is added.

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?

Three short sentences, front-loaded with the core action and immediately followed by the practically important id-mapping note. The trailing 'Read only' duplicates the annotations and could be dropped without loss.

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?

An output schema exists, so return-shape explanation is unnecessary, and the description covers the two things an agent actually needs: what set is returned and what the ids are for. A small gap remains around ordering or whether the list can be empty, but nothing essential is missing for a zero-argument read.

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, so the baseline is 4. Nothing about arguments needs clarifying, and the description correctly spends its words on the scope of the returned set instead.

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 ('Lists the Paidnice organisations') and adds scope that matters: only those this connection can use, plus a per-entry write-permission flag. This is enough to separate it from the singular sibling get_organisation, though the description never names that alternative explicitly.

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?

'Their ids are the organisationId the other tools take' gives a concrete reason to call this first — to obtain an id required elsewhere. It stops short of explicit exclusions (e.g. 'use get_organisation when you already have an id'), so it is strong context rather than a full when/when-not rule set.

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