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

The description carries rich behavioral detail beyond the readOnlyHint annotation: login requirement, newest-first ordering, cursor pagination until null, cards limited to the latest two comments, truncation handling by reducing limit, mutual-follow requirement for friend content, and empty results for blocked/deactivated users. These are exactly the traits an agent needs before calling a feed tool.

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?

The description is densely front-loaded with the login requirement and core behavior. It is highly concise, though the telegraphic phrasing and unclear fragment '首页total/muted' slightly reduce readability.

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 still explains return shape constraints (card comments), pagination termination, truncation behavior, permission-based empty results, and follow-up tools. It is complete enough for an agent to call the tool correctly.

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 the baseline is 3, but the description still adds operational meaning: cursor should be passed through until null, truncation should be handled by reducing limit, and omitted userId means self. Some of this duplicates the schema, but the pagination loop and truncation workaround are useful additions.

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 a specific resource and scope: '某人动态，缺省本人' (someone's moments, defaulting to yourself). It is clear this is a read/list operation, but it does not explicitly distinguish itself from close siblings like list_moments_feed or search_moments.

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 useful context: login required, defaults to self, and routes to get_moment for full text, get_creator to view the person, and start_conversation to contact. It lacks an explicit statement of when to prefer this over list_moments_feed or search_moments.

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