Create an OpenClaw invite prompt bundle

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

Annotats indicate it's not read-only, not destructive, and not idempotent. The description adds no behavioral context beyond the HTTP method and authorization. No contradiction with annotations.

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?

Very short (2 sentences) but the first sentence repeats the title wastefully. It is concise but lacks substance.

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?

Despite having an output schema, the description fails to explain what the bundle is, what the body parameter does, or how to use it. Incomplete for a creation tool with two required parameters.

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 description coverage is 0%. The description does not explain the parameters (companyId, agentMessage) at all, leaving the agent to rely solely on the schema structure.

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 identifies the action ('Create') and resource ('OpenClaw invite prompt bundle'). The purpose is specific and distinguishes this tool from sibling company-related tools, though the term 'OpenClaw' is unexplained.

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 on when to use this tool versus alternatives, such as generic invite tools. Only technical details (HTTP path and auth class) are provided.

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