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

No annotations are provided, so the description carries full burden. It discloses the output format (JSON ready for PDF) but lacks details on side effects, size limits, rate limits, or whether the report is generated on demand or fetched. Minimal behavioral context.

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 a single sentence that is concise but lacks structure (e.g., bullet points or separate sections). It efficiently conveys purpose but could be more organized.

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 minimal schema (one parameter, no output schema, no annotations), the description is incomplete. It fails to mention return value structure, error conditions, prerequisites (e.g., must have completed analyses), or input format details. The tool's usage context is insufficiently addressed.

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 input schema has one parameter (ideaId) with no description coverage from the tool description. The description does not explain the parameter's meaning, format, or constraints beyond what the schema already provides. This adds no value.

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 the verb 'Export' and the resource 'a complete idea report' with specific contents (scores, validations, etc.), and specifies the output format (clean JSON for PDF). This distinguishes it from sibling tools that generate individual components like competitor analysis or market fit.

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 implies this tool is for exporting the full report, but does not explicitly state when to use it versus the sibling tools (e.g., use after individual analyses are complete). There is no mention of prerequisites or exclusions.

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