document_intelligence_create_report

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

With no annotations, the description must disclose behavioral traits. It mentions routing and auth scope but does not state whether the tool is read-only or creates persistent state, nor does it describe side effects or output structure. The existing schema coverage is 0%, so the description adds little about behavior.

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 relatively short but includes redundant technical routing details ('Routes through the platform's domain-agent dispatcher') that do not aid an AI agent in selecting or using the tool. Could be more concise by focusing on the report creation purpose.

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?

Given the existence of an output schema (context signal), the description avoids explaining return values but still fails to clarify the tool's role among numerous document_intelligence siblings. It does not specify when to use this tool over others like create_marketing_collateral or write_document.

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 description adds meaning to the two parameters: 'message' as free-text objective and 'inputs' as optional JSON. This compensates for the 0% schema coverage, but it does not explain the expected JSON structure or provide constraints, leaving interpretation open.

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 states the tool runs a domain agent action to create a report, but it lacks specificity on what kind of report or how it differs from sibling tools like document_intelligence_write_document or create_spreadsheet. The verb 'create' is clear, but the resource 'report' is vague.

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 on when to use this tool versus alternatives. The description does not mention prerequisites, when not to use it, or compare to similar tools in the document_intelligence family.

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