yg_task_chat_get

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

Description implies read-only behavior but lacks detail on auth, rate limits, or pagination. With no annotations, the description should cover more behavioral specifics.

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?

Two sentences, front-loaded with verb and resource, and no wasted words. Could be slightly more structured but is efficient.

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?

Fails to explain return format, pagination behavior, or the effect of includeSystem beyond its basic description. Lacking output schema, the description should provide more context.

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?

Clarifies that taskId equals chatId, adding value beyond schema. However, with only 25% schema coverage, description does not compensate for undocumented parameters (limit, offset).

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 reads chat/comments of a task, using task ID as chat ID, distinguishing it from task retrieval and comment creation siblings.

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?

Only a vague hint 'useful for watching discussion' is provided; no explicit when-to-use, when-not, or alternatives are mentioned despite sibling tools like yg_task_get and yg_task_comment.

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