get_deep_analysis_status

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

With no annotations, the description carries the transparency burden. It explicitly states that progress is checked and full results are only returned when the job is complete, implying intermediate status responses. It does not disclose auth, rate limits, or error behavior, but for a simple status check tool, these are less critical.

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 a single, well-structured sentence that front-loads the main action ('Check deep analysis progress') and explains the conditional outcome. Every word earns its place with no redundancy.

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 simple one-parameter tool with no output schema, the description adequately conveys the purpose and the key behavioral distinction between progress and completion. It could be more explicit about the return format or that it may be polled, but given the tool's simplicity, this is largely complete.

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 only parameter upload_id is fully described in the schema as 'returned by a prior validation workflow.' The tool description adds no additional meaning beyond the schema, so it earns the baseline score for high schema coverage.

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 checks deep analysis progress and returns full domain-level results upon completion. It uses a specific verb ('check') and resource ('deep analysis progress'), distinguishing it from siblings like trigger_deep_analysis or get_smtp_status.

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 implies this tool should be used after triggering deep analysis and potentially polled until completion. It gives clear context on what it does, though it does not explicitly exclude alternatives or state when not to use it. The sibling tool trigger_deep_analysis is an obvious complement but not mentioned.

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