smokeball_add_layout_contact

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

No annotations provided, and description does not disclose behavioral traits such as whether the operation is destructive, requires specific permissions, or what side effects occur. The generic routing info adds no value.

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 short but wastes space on generic routing details common to all tools. It fails to provide essential functional information, making it under-specified rather than concise.

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 presence of an output schema and the need to understand what the tool does, the description is completely inadequate. It does not explain the operation, required inputs, or expected outcomes, leaving the agent without enough context.

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?

Input schema has one parameter 'arguments' (JSON string) with 0% description coverage. The description only restates 'JSON string of arguments for the connector operation' without specifying expected keys or format, offering minimal help beyond the schema.

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?

Description merely states the tool name and that it's a 'connector operation' without explaining what 'add_layout_contact' does. It does not distinguish this from sibling tools like smokeball_create_contact or smokeball_get_layout_contacts; purpose is vague and confusing.

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. For instance, it doesn't clarify whether this is for adding a contact to a layout or creating a new contact; without context, agent cannot decide when to invoke it.

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