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

readOnlyHint=true already tells the agent this is a safe read, so the burden is light. The description does add value by naming the two notable fields returned (online state, door-unlock config), which hints at the response shape. It says nothing about whether unpaired/offline kiosks are included, ordering, or pagination for what could be a long list.

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 front-loaded clause with zero filler; the scoping ('paired to a gym') comes before the parenthetical field hints. Slightly fragmentary — it reads more like a subtitle than a complete instruction, but 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?

For a one-parameter read-only list with annotations covering safety and no output schema, this is close to sufficient: the agent knows the org id input and roughly what comes back. Minor gaps are ordering/empty-result behavior, which are unlikely to change how the tool is called.

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?

With one parameter at 100% schema coverage — and the schema itself pointing to list_my_organizations for the id — the schema does all the work. The description adds no semantics about organizationId beyond what is already structured, so baseline 3 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 the resource precisely — 'check-in kiosks paired to a gym' — and the parenthetical ('online state, door-unlock config') clarifies what data the listing covers, distinguishing it from create_gym_kiosk/revoke_gym_kiosk/set_gym_kiosk_door which act on a single kiosk. The verb 'list' is only implied rather than stated, but the resource scope is unambiguous.

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 implied by the name and the 'paired to a gym' scoping, but there is no explicit statement of when to reach for this versus revoke_gym_kiosk or create_gym_kiosk, and no prerequisites (e.g. org admin access) are noted. An agent can infer the use case but gets no routing help.

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