document_intelligence_create_sales_collateral

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

No annotations are present, so the description must carry the full behavioral burden. It mentions routing and scope but fails to disclose side effects, required permissions, or whether the tool is destructive. For a creation tool, this is insufficient.

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 concise (three sentences plus parameter list) and front-loaded with the action name. However, it could be more structured by separating behavioral notes from parameter descriptions.

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 but the description omits any explanation of return values. For a creation tool, the agent likely needs to know what is returned. The description compensates for low schema coverage on parameters but lacks output context.

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?

With 0% schema coverage, the description adds significant meaning: 'message: Free-text objective' and 'inputs: Optional JSON string of structured inputs.' This clarifies both parameters beyond their names and defaults.

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 it runs the 'create_sales_collateral' action, distinguishing it from siblings like 'create_marketing_collateral' via the tool name. It specifies the scope (JWT, tenant, company) and that it routes through a domain-agent dispatcher.

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 does not provide any guidance on when to use this tool versus alternatives (e.g., document_intelligence_create_marketing_collateral). It only mentions routing and scope without contextual usage advice.

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