Attach company analysis

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

Disclosures destructive behavior (replaces previous), size limit (100KB), and user-facing purpose (dashboard). Complements annotations (destructiveHint=true) without contradiction.

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?

Multiple sentences each adding value (size limit, replacement behavior, usage context). Example is helpful but slightly extends length; overall efficient.

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?

Fully covers all key aspects for a two-parameter tool: purpose, replacement semantics, size constraints, and end-user consumption, needing no further clarification.

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 has minimal description for 'markdown'; description adds context that it is 'company analysis (research you produced)' and provides a concrete example, compensating for low schema coverage.

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?

Clear verb ('Attach') + resource ('company analysis') + destination ('to an application'). Distinguishes from sibling 'attach_file' by specifying markdown analysis content.

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?

Explicitly states 'Single document per application - a new call REPLACES the previous one', providing clear usage context. Lacks explicit mention of when not to use, but context is strong.

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