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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), and the description adds genuinely new traits: no model calls are consumed, and the call neither authorizes background polling nor schedules work. What is missing is any indication of what the compact status payload contains or how it relates to the thread state.

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?

Three short sentences, no filler, and the core capability is stated first. The final sentence about polling/scheduling is a constraint rather than padding, so it earns its place, though the opening phrase "compact own status" is compressed to the point of obscurity.

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?

With one required parameter, no output schema, and annotations already declaring the safety profile, the description covers the essentials: how to obtain thread_id, what to do with it next, and what the tool will not do. The one gap is that it never describes what the returned status actually contains, forcing the agent to call it blind.

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% for the single thread_id parameter, so the description must carry the load. It usefully documents provenance ("the returned thread_id"), telling the agent where the value comes from, but adds nothing about the required dsc_ format or the pattern constraint already in the schema.

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?

"Read compact own status without model calls" states a read operation but leaves the resource ambiguous — it never says the status is an investigation's status, and the reader must infer that from the tool name and title. The second sentence clarifies that the result feeds collaboration tools, which partially distinguishes it from siblings, but the core resource is underspecified.

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 a downstream usage pattern (pass the returned thread_id to collaboration_changes and collaboration_messages to fetch only new replies) and one explicit exclusion ("does not authorize background polling or schedule any work"). However, it never says when to call this versus siblings like collaboration_thread, get_research_request, or get_outcome, so the selection guidance is implied rather than stated.

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