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

Annotations only declare readOnlyHint=true, but the description adds login requirement, return contents (full text, likers, first 50 comments in ascending order), error normalization to moment_not_found for deleted/visibility/blocked cases, and the attached-card type dispatch 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?

Organized into three labeled, front-loaded sections (login/return, composition chain, error semantics) with no filler. Every sentence carries actionable information for an agent.

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 single-param, read-only detail tool with no output schema, the description covers return contents, ordering and limits, required auth, error behavior, and next-step tool chaining. Nothing essential 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?

Schema description coverage is 100%, and the momentId schema already documents that the ID comes from list_moments_feed, get_user_moments, or search_moments. The description adds no further syntax or format guidance beyond the schema, so the baseline of 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?

States a specific verb and resource: it returns the full text, likers, and first 50 comments (chronological) of one moment. This clearly distinguishes it from list_moments_feed, get_user_moments, and search_moments, which all return moment IDs rather than full detail.

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?

Explicitly says to call it before replying to a comment in order to get commentId, and names the follow-up tools comment_moment and like_moment. It also explains the card-dispatch chain to get_activity/get_product/get_need/get_organization when available=true.

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