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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses real behavior: attendees come newest first, each carries a wallet and badge-landed flag, the claim url is null with the reason surfaced in 'share' until claiming is live, and the claim word is write-only and cannot be read back. That is meaningful context annotations cannot express; only pagination/limit behavior is left to the schema.

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?

Information-dense but delivered as one long run-on sentence with stacked parentheticals, which makes the key points (null url semantics, non-readable claim word) harder to parse than they should be. Nothing is padding, but the structure could be broken into front-loaded clauses.

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 output schema, the description carries the burden of describing the return shape, and it does: settings, claim link state, and attendees with wallet and badge status. For a read-only, two-parameter tool this is close to sufficient; only the list-vs-detail routing 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?

Schema coverage is 100%, so both parameters (id format, limit default/max) are fully documented upstream. The description reinforces that the limit governs attendee count via 'attendees, newest first' but adds no new semantics such as ordering direction or range, so 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?

The description names a specific resource and scope: 'One Moment the link owner hosts', including settings, claim link, and attendees. That is far more specific than the title alone, though it never names a sibling (my_moments, moment) as the alternative; that routing cue lives only in the schema text ('my_moments lists them').

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 implied rather than stated: the agent can infer this is the single-Moment detail read versus the list tool, and the claim-link caveat hints at when it's useful. There is no explicit when-to-use or when-not-to-use guidance in the description itself.

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