Adobe Firefly Debug Bundle

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It clearly states the tool is read-only and enumerates actions it never performs (click Generate, upload, modify, navigate away). This gives agents strong safety guarantees, though it does not mention potential consequences like collecting sensitive data or time to execute.

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 only two sentences, every sentence adds value: the first states the core action, the second provides read-only affirmation and usage guidance. It is front-loaded with the essential purpose and extremely concise with no wasted words.

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 complexity of a debug bundle (26+ files), the description covers its behavior, safety profile, and typical use cases. While it does not enumerate specific diagnostic files, the agent likely has enough context to invoke it appropriately. No output schema exists, so explaining return values is not required.

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?

There is one optional parameter (url) with 100% schema description coverage, so the baseline is 3. The tool description does not add any additional meaning about the parameter beyond what the schema already provides. It does not explain how the url parameter affects the debug bundle capture.

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 captures a comprehensive debug bundle with 26+ diagnostic files, and explicitly distinguishes itself from sibling tools by declaring it never clicks Generate, uploads files, modifies settings, or navigates away. This makes the tool's specific purpose unambiguous.

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 explicit use cases: 'diagnose automation issues, validate selectors, check auth state, and inspect browser environment.' It also implicitly contrasts with other tools by listing what it does not do. However, it does not explicitly name alternative sibling tools for different tasks, such as 'use firefly_generate for generating images.'

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