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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds genuinely new behavior: results are still produced when the machine is offline, and lock is null in that case, when no rule exists, or on a public app. It also explains that group rules carry group_name and group_people alongside the group id.

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?

Front-loaded with the core action, then a compact block of edge-case semantics. Dense but each clause carries information; the long middle sentence could be split but nothing is filler.

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 carries the return-value burden and does so well, describing the rule fields and the null-lock cases. The remaining gap is that it does not mention ordering or result size for a machine with many rules.

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 description coverage is 100% and both parameters (node_id, service_name) are documented in the schema, including the pointer to nerdit_list_nodes. The description adds only the framing that the app must be private, so the baseline of 3 is appropriate.

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 precise verb and resource: list the access rules granting non-owner access to one private app, and enumerates the returned fields (id, kind, value, live sessions, lock). This cleanly distinguishes it from the mutating siblings nerdit_grant_app_access and nerdit_revoke_app_access.

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?

The context of use is clear from the opening clause, and it usefully notes the offline case ('Works while the machine is offline; lock is then unknown'), which tells the agent when results are partial. It never names an alternative tool or an explicit when-not-to-use condition, so it stops short of a 5.

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