dealdesk.export_intelligence

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

With no annotations, the description carries the full burden but adds little: 'Bounded export path' gestures at a limit without explaining it. It doesn't state permissions, whether the export is synchronous, size/time limits, or how results are delivered.

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?

Two short sentences, front-loaded with the core purpose. However, the trailing 'Bounded export path' is vague filler that doesn't earn its place.

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 an export tool with no annotations, no output schema, and partially documented params, the description is too thin. It omits what the file contains, how it's returned, and the constraints implied by 'bounded'.

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 coverage is 67%; two enum params (view, source) are only partially described and 'source' has no schema description at all. The description adds no parameter meaning and doesn't compensate for the gaps.

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?

States a specific verb (Export) and resource (Deal Intelligence workbook) plus the output format (Excel). An agent can distinguish it from the many list/get/create siblings, though it doesn't name any sibling or explain scope boundaries.

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?

Only 'for analysis' hints at a use case, and 'Bounded export path' is opaque. There is no statement of when to use this vs. the render_*/get_* siblings, no prerequisites, and no exclusions.

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