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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing that membership is scoped to the link owner rather than the caller-supplied identifiers, and that names/descriptions are untrusted user-generated content to be treated as data. It stops short of covering result size, ordering, or pagination behavior.

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?

Two sentences, both load-bearing: the first defines the resource and its fields, the second carries the injection-safety caveat. Nothing is repeated from the schema or annotations, and the substantive content 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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does state the member/role/studio shape plus the trust caveat. Minor gaps remain around empty-team behavior and result limits, but nothing critical is missing for a called-with-no-arguments read tool.

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?

The tool takes zero parameters, which is the baseline-4 case. The description reinforces this by framing the scope as 'the link owner's' team, making clear no identifier argument is expected.

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 states the resource (the link owner's FloorFeed Badges team) and the returned information (members, their roles, and the studios they joined), so an agent knows exactly what it is asking for. It does not name or contrast any sibling such as my_badge_game or my_soulbound_badges, so the differentiation is left to the tool name prefix.

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?

Usage is only implied: because there are no parameters and the subject is 'the link owner's' team, an agent can infer it needs no identifiers and applies to the current context. There is no explicit statement of when to prefer this over related roster tools, nor any prerequisites or exclusions.

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