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

The description discloses important behavioral traits beyond the annotations: async execution (1-2 minutes), returning a processing handle, requiring a follow-up status call, and instructing the agent to tell the user it is running. This significantly extends the readOnly/openWorld hints from annotations.

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 two sentences long, front-loaded with the core purpose, and every clause earns its place—including the essential async behavior and user-facing instruction. It is concise without omitting critical operational details.

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 complex analysis tool with no output schema, the description explains what it returns (structured summary), how to handle the async flow, and the next step (status call). It is sufficiently complete for an agent to invoke correctly and manage expectations.

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% for both parameters (proceeding_number and quick_mode). The description does not add meaningful parameter-level information beyond what the schema already provides, so the baseline of 3 is appropriate.

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 a specific verb ('Analyze'), resource ('TTAB proceeding'), and depth ('in depth'), with detailed outputs (timeline, party positions, strategic assessment). It distinguishes itself from siblings like get_ttab_proceeding_details and get_ttab_document by emphasizing analysis rather than retrieval.

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 provides clear context on what the tool does and the async workflow (returns a processing handle, then call get_ttab_proceeding_analysis_status). It does not explicitly mention alternatives or when-not-to-use, but the guidance is sufficient for an agent to understand the intended use case.

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