Browser Run Canva Action

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

The description honestly discloses that the tool is a non-functional stub due to a missing browser-automation dependency (e.g., Playwright). This goes beyond annotations and explicitly warns the agent that invoking it will fail, which is useful 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, but it is under-specified rather than concise. It omits all functional details and reads as a placeholder, not as a deliberately streamlined explanation.

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 a tool with three required parameters and no output schema or annotations, the description is drastically incomplete. Even acknowledging it is a stub, it does not clarify the intended purpose, parameter meaning, or outcome, making it unusable for selection or invocation.

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 provides zero information about the three required parameters (action, target, reason). With 0% schema coverage and no parameter descriptions, the agent has no clue what these strings mean or how to fill them.

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 name implies a browser automation tool for Canva, but the description only states it is not implemented and does not define any actual functionality. There is no verb or resource described, leaving the agent unable to understand what the tool would do if it were available.

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?

No guidance is provided on when to use this tool or which alternative to choose instead. The description merely says it is not implemented, implicitly discouraging use, but does not name any sibling tools as substitutes.

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