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

The description discloses a genuine behavioral constraint not present in the annotations: JWT authentication is required. It also previews the returned fields. However, it says nothing about mutation/reversibility semantics, and the readOnlyHint=false annotation sits oddly against what reads like a pure lookup, leaving the safety profile slightly ambiguous.

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 with zero waste: precondition first, then payload contents, then the sibling escape hatch. Every clause earns its place and the most important constraint (JWT) is front-loaded.

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?

There is no output schema, so the description usefully enumerates the returned fields (rank, score, Studio access, legacy plan) and states the auth requirement. For a parameterless read tool this is nearly sufficient; a note on whether it 404s or errors when no membership exists would close the remaining gap.

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 parameters, the baseline is 4; there is nothing for the description to clarify. It correctly avoids inventing parameter detail and instead uses the space for output contents.

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 exact resource (your Network membership record) and enumerates its contents: rank, score, Studio access, and any legacy plan still honoured. It also distinguishes itself from the sibling attention_me, which covers the board row. The only shortfall is that the retrieval verb is implied rather than stated.

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 an auth prerequisite ('Requires a JWT') and an explicit routing rule pointing to attention_me for the board row, which is concrete when-not guidance. It does not, however, situate this against the many other '_me'/'report' siblings (network_report, network_member_report, affiliate_me), leaving that comparison to inference.

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