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

Beyond the annotations (readOnlyHint, idempotentHint, non-destructive), the description discloses a non-obvious behavioral trait: structured records appear a couple of minutes after a conversation ends, so processing=True means 'still processing' and False means 'nothing was captured'. That latency/interpretation context is exactly what annotations cannot convey.

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?

Front-loaded with the core definition, then a compact explanation of why it beats guessing from an empty list. The trailing 'Args:' line largely duplicates the schema text, which is minor waste, but the rest of the prose earns its place.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, the timing caveat, result interpretation, and the one parameter. Nothing an agent needs to call this correctly is missing.

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 100% and the single optional agent_id parameter is already documented in the schema. The description only restates it as 'Optional narrowing to one agent', adding no format, ID type, or default nuance beyond the structured field. Baseline 3 applies.

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?

States a specific check ('whether any conversation capture is still being extracted') with a clear resource and scope. It also implicitly separates itself from gnosari_collected_data by explaining that an empty collected-data list is ambiguous while this tool resolves it. An agent can pick between the two without opening a schema.

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?

Gives concrete when-to-use context: consult it to answer 'has the data landed yet?' rather than inferring from an empty list, and states the two result interpretations (still processing vs. genuinely nothing captured). It does not name the sibling tool (gnosari_collected_data) explicitly, but the condition that selects it is clear.

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