Goora Travel Posts / 旅行帖子

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

The annotations already declare this operation is read-only, idempotent, open-world, and non-destructive, so the description does not need to restate the safety profile. It then adds genuinely new behavior: public visibility and safety status are rechecked live at call time, private or withdrawn posts come back empty, so the call may legitimately fail to return data. It also disambiguates contentStatus=image-or-title-only as 'no text body supplied' to prevent the agent from inferring image facts.

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?

Four dense sentences, with no filler: first the core action and input source, then the live-availability caveat, then output-citation guidance, then a semantic warning about contentStatus. The most important constraint (how post_id is obtained) 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?

For a single-parameter read tool with no output schema, the definition covers what is needed: input provenance, live recheck behavior, and key return-field semantics such as contentStatus and url/modifiedAt. The only thing it does not address is return shape or size, but that is most likely outside the definition's scope.

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 for this single parameter is 0%, and the schema only defines a pattern. The description compensates by describing post_id as an exact string that must be obtained from a prior search, which warns against constructing or guessing IDs. It does not cover the pattern's length or character constraints, but it does add enough meaning to make the parameter usable.

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?

It names a specific verb and resource ('Read a Goora public travel post'), and it identifies which input selects the post, namely the exact string post_id returned by search. This makes it directly distinguishable from the sibling search_goora_posts: this tool is the per-post retrieval step that follows a search.

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?

By saying the post_id must be 'returned by search', the description implies when to use this tool (after search_goora_posts) and that post_id must be used as an exact string rather than fabricated. It also states that private or withdrawn posts are not returned. The only gap is that it does not explicitly name search_goora_posts as the alternative for discovery.

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

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

Annotations already establish readOnly/idempotent/openWorld and non-destructive behavior, so the description's added value is in disclosure of result behavior: live-checked posts, source URLs, update times and text availability. It also discloses the AND semantics for space-separated keywords, which is genuine behavioral information not present in 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?

The definition is compact and front-loads the primary use case, followed by query syntax, then return content, then exclusions. The bilingual phrase pairs add length but serve a matching purpose rather than padding.

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?

There is no output schema, and the description does describe return contents (URLs, update times, text availability), which covers the biggest gap. Still missing is pagination behavior for offset/limit and the meaning of an empty query, both of which an agent needs in order to page or run an unfiltered search 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 description coverage is 0%, so the description must carry parameter meaning. It partially does: 'query' semantics (short destination/topic keywords, space-separated terms must all match) are explained, but limit and offset receive no explanation at all, and the empty-string default for query is left unexplained (does it return unfiltered posts?).

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 concrete resource (Goora public community posts for destination planning, citywalk, family trips) and the action of finding/sourcing them, which is distinct from the sibling get_goora_post's single-post retrieval. It stops short of explicitly contrasting itself with that sibling, but the retrieval scope is unambiguous.

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 positive when-to-use context (destination planning, citywalk, family trip research) and explicit when-not-to-use exclusions (not current inventory, bookings or payments). However, it never routes the agent to the sibling get_goora_post for fetching a specific post, and gives no guidance on how to use offset/limit when results are insufficient.

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