company_reviews

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

The description implies both read ('inspect') and write ('advance') capabilities but does not disclose side effects, permission requirements, reversibility, or operational consequences. With no annotations provided, the description fails to convey behavioral expectations beyond this minimal hint.

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 consists of a single short sentence, which is concise in length, but the use of unexplained jargon ('scoped lifecycle', 'verified receipts') makes it less clear than it could be. It achieves brevity at the expense of comprehensibility.

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 a 7-parameter schema and 2 required parameters, the description provides no context about required inputs, available operations, expected outputs, or the overall purpose of the tool. It is far from enabling correct usage without additional information.

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 schema defines seven parameters without descriptions, and the tool description offers no elaboration. Terms like 'operation', 'entity_ref', 'bundle_json', and 'payload_json' are left entirely unexplained, so an agent cannot determine what values are appropriate or required.

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 says 'Inspect or advance reviews' but leaves critical terms undefined: what constitutes a 'review', what 'advance' means as an action, and the meaning of 'scoped lifecycle' and 'verified receipts'. This is too vague to confidently select the tool over similar review/approval 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?

No guidance is provided on when to use this tool versus the many sibling tools that deal with reviews, approvals, or lifecycle actions (e.g., list_pending_approvals, approve_task). The description does not differentiate its purpose or recommend usage scenarios.

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