check_review_status

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

No annotations are provided, so the description must fully cover behavioral traits. It only describes the return value and the calling context, but fails to disclose side effects (e.g., whether it modifies state), error conditions, idempotency, or permission requirements. For a tool that likely performs a read operation, this omission is a significant gap.

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 extremely concise: two sentences with no extraneous information. It is front-loaded with the key return value and the usage context, making it easy to parse.

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 has an output schema (not shown but flagged as present), the description does not need to detail return values. It provides the calling context (dashboard on_mount) and purpose (sync with checkpoint). However, it lacks details on error handling, performance considerations, or any constraints, which would be helpful for completeness.

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?

The input schema has one required parameter 'thread_id' with no description (schema coverage 0%). The tool description does not explain the semantics of 'thread_id' beyond referring to 'a thread'. An agent needs to know what a valid thread_id looks like (e.g., format, source) to use it correctly.

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 returns a tuple of {reviewed, decision_result} for a thread, which is a specific verb and resource. However, it does not explicitly differentiate from sibling tools 'ask_agent' and 'resume_review', though the difference is implied by the context (dashboard sync vs. agent interaction or review continuation).

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 provides a specific usage context ('Called from the dashboard's on_mount...') and mentions the reason (sync with LangGraph checkpoint after iframe remount). However, it does not explicitly state when not to use the tool or mention alternative tools for different scenarios.

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