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

No annotations are provided, so the description carries the full burden of behavioral disclosure, but it discloses nothing about side effects, authentication, long-running behavior, or return values. The sentence merely names the tool and equates it with a catalog entry.

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 short, but shortness is not conciseness when the content is uninformative. The only substantive clause points to a catalog URL, which does not help an agent invoke the tool. Every sentence should add value, and this one does not.

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 no annotations, no output schema, an open input schema, and a generic name, the description leaves almost all invocation context missing. An agent cannot know what inputs to pass, what the tool returns, what it analyzes, or what side effects to expect. This is critically incomplete.

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 schema has zero declared parameters and 100% coverage, so there are no parameter descriptions needed. The baseline for zero-parameter tools is 4, and the description does not mislead about parameters. However, the schema allows additionalProperties, so some clarification of accepted inputs would have been helpful, but this is not required by the baseline.

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 only restates the tool name and points to a live catalog URL; it never states what run_document_intelligence actually does. An agent cannot infer whether this invokes an AI document analysis, runs OCR, or triggers a background job. It provides no verb or resource that would distinguish it from siblings like run_data_extraction or run_statement_qa.

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?

There is no guidance about when to use this tool versus any of the many run_* sibling tools. The reference to the live catalog is not a usage condition or selection criterion. An agent has no basis for deciding to call this tool.

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