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 description's obligation is reduced. It adds the underlying REST call (GET /v1/users) and the returned field set, but says nothing about pagination behavior, rate limits, or result size — the schema covers cursoring but not the behavior around it.

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 sentence with zero padding, and the returned-field list sits right after the resource. The trailing REST path restates what the verb already conveys, which is mildly redundant but harmless for an agent that reasons over HTTP endpoints.

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?

This is a simple, zero-required-parameter read with no output schema, so the description's listing of returned fields (id, name, email) usefully compensates for the absent return contract. It is nearly complete, needing only a word on pagination or result ordering.

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%: limit's range/default and cursor's nextLink convention are both fully documented in the schema. The description adds no parameter meaning beyond that, so the 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?

Names a concrete verb and resource ('List users in the Folk workspace') and enumerates the returned fields (id, name, email), which sets it apart from the note/company/person siblings. It does not explicitly distinguish itself from the closest sibling, folk_get_current_user, so it stops short of a 5.

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?

'Useful for resolving owner ids' implies the intended scenario but gives no explicit when-to-use rule, no exclusions, and no named alternative (e.g. get_current_user vs a full user list). Usage is inferred rather than stated.

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