jotify_list_recent_posts

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It reveals that only public posts are returned and that they are recent, implying a read-only operation. However, it does not explicitly state safety (e.g., no side effects), authentication requirements, or pagination behavior beyond the limit parameter. It adds some value but is not comprehensive.

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 a single, concise sentence that front-loads the core purpose and then adds the key filtering option. Every word contributes to the meaning; there is no filler or redundancy, making it highly efficient for AI parsing.

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?

Given the tool's simplicity (2 optional parameters, no output schema), the description adequately covers the essentials: what the tool does, the data scope (public and recent), and the filtering dimension. It could be improved by explicitly stating the output structure or ordering, but the phrase '最近发布' implies recency sorting. Overall, it is sufficiently complete for a basic list query 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?

Schema description coverage is 100%, so both parameters are already documented. The description reinforces the tag filter by mentioning '#topic/tag', which adds minimal additional meaning. The limit parameter is not mentioned in the description, but the schema already covers its default value and role. Since the schema handles the semantics, this dimension is at baseline.

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 clearly states the tool's purpose: to query the list of recent public posts on the Jotify Moment platform, with optional tag filtering. It uses specific verbs ('查询' meaning query/list) and a distinct resource ('公开动态列表' - public posts list), effectively distinguishing it from siblings like create_post or upload_media.

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?

The description explicitly mentions the filtering capability by #topic/tag, indicating when to use this parameter. However, it does not explicitly state when to use this tool versus alternatives (e.g., for retrieving a single user's profile), though the name and purpose make the use case clear. It provides context (recent public posts) without exclusions or integration guidance.

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