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

readOnlyHint and destructiveHint already declare the safety profile, so the description earns credit for adding what annotations cannot: the required "read scope" for authorization and the fact that each set carries member ids usable in another tool. It does not cover ordering or set-size behavior, but the gaps are minor.

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 what is returned, then the actionable use of the output, then the auth requirement. Nothing is repeated from the title or annotations and no sentence 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?

An output schema exists, so return values need not be spelled out, and a zero-parameter tool has little else to document; the auth scope note closes the main practical gap. Ordering of the returned sets is unaddressed, which is the only real omission for an agent deciding how to consume 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?

With zero input parameters the baseline is 4, and the description goes slightly beyond by explaining what the member ids in the response are for. The referenceId advice refers to jobs_create's parameter rather than this tool's, so it informs output semantics more than input semantics.

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?

The description names the resource precisely ("the creators, competitors and peers this account works from, by set") and enumerates the returned fields, so an agent knows exactly what comes back. It does not, however, distinguish itself from close siblings such as references_browse, reference_search or reference_read, so the verb+resource is clear but the boundary is not.

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?

It gives one concrete downstream usage (pass a member id as referenceId to jobs_create), which is genuinely useful routing context. But it never says when to pick this over references_browse / reference_search / reference_read, leaving the main selection decision to inference.

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