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

Annotations only declare readOnlyHint, so the description adds real value: it discloses the response shape (userId, email, name) despite there being no output schema, and flags the call as cheap, which supports using it as a credential preflight. It does not describe failure behavior (e.g. auth errors) or rate limits, keeping it short of a 5.

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, each earning its place: what it returns, why to call it, and the underlying endpoint. The return fields are front-loaded before the rationale.

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 zero-parameter, read-only tool with no output schema, the description covers everything needed: the identity of the resource, the fields returned, and the practical reason to invoke it. Nothing required for correct invocation is missing.

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?

Zero parameters, so the schema has nothing to document and by rule the baseline is 4. The description correctly adds no parameter text, and the parenthetical field list describes output, not input.

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?

Specific verb+resource: returns the authenticated staff user, with the returned fields (userId, email, name) named inline. The 'acting as' framing cleanly separates it from sibling momence_get_member, which fetches an arbitrary member rather than the credential principal.

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?

'A cheap way to confirm the credentials work' gives a concrete use case, so the agent knows when this is the right call. It stops short of naming an alternative or stating when not to use it, but for a zero-arg identity probe the context is clear.

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