document_intelligence_create_marketing_document

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

With no annotations, the description must disclose behavioral traits. It only mentions authentication/authorization routing (JWT, tenant, company scope) but omits what the tool actually does to create a document, whether it overwrites, requires specific permissions, or produces output.

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 brief and structured with an 'Args' section. The first sentence is somewhat redundant with the tool name, but overall it is efficient and easy to parse.

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?

The description fails to provide enough context for an agent to select this tool over similar ones. It does not mention output, side effects, or what distinguishes a marketing document from other document types. The presence of an output schema is noted but unused.

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 basic meaning to both parameters: 'message' as a free-text objective and 'inputs' as an optional JSON string. Given 0% schema coverage, this is helpful but lacks details on expected format or constraints.

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 merely restates the action name 'create_marketing_document' without explaining what a marketing document is or how it differs from other document creation tools. It focuses on routing details rather than the tool's core purpose.

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 no guidance on when to use this tool versus its many siblings (e.g., document_intelligence_create_marketing_collateral, document_intelligence_create_report). No context, prerequisites, or alternative recommendations are given.

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