zhiqi_collab_timeouts

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

With no annotations, the description carries the full burden of behavioral disclosure. 'View' weakly implies a read-only operation, but the description does not mention whether it is safe, what side effects might occur, how results are scoped, or what the output looks like.

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 short, but brevity here is under-specification rather than effective conciseness. It occupies minimal space but omits essential guidance, so it does not earn its place as a complete description.

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 tool with one optional parameter and no output schema, the description is incomplete. It fails to clarify the meaning of 'scope', the difference between 'mine' and 'against_me', or what the returned timeout records contain.

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%, and the description does not compensate. The optional 'scope' parameter with enum values 'mine' and 'against_me' is left unexplained; the agent must infer its meaning solely from the schema enum.

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 states a clear verb ('view') and a specific resource ('timeout records'), so an agent understands the basic operation. It does not explicitly differentiate from sibling tools, but the resource is unique enough in the sibling list to avoid obvious confusion.

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 given for when to use this tool versus alternatives such as zhiqi_collab_status or zhiqi_collab_policy. The description implies a read operation but provides no context on selection criteria or exclusions.

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