send_checklist

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

Annotations already declare the tool as non-readonly, open-world, non-idempotent, and non-destructive. The description adds the important precondition that a business connection is required, but it does not describe side effects, visibility, error behavior, or response details. With annotations covering the safety profile, this is adequate but thin.

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?

Two short sentences, front-loaded with the action and followed by the prerequisite. There is no unnecessary wording, though the extreme terseness leaves the structure minimal.

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 an 8-parameter send tool with low schema coverage and no output schema, the description is materially incomplete. It omits the checklist payload format and most parameter usage details, leaving an agent unable to call the tool correctly from the description alone.

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 only 38%, and the description does little to compensate. It alludes to the required business_connection_id without naming it or explaining how to use it, and it gives no meaning for the critical empty checklist parameter or the other undocumented parameters.

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?

States a specific verb ("Send") and resource ("interactive checklist"), so it is not a tautology. It does not differentiate from siblings such as send_message or edit_message_checklist, but the operation is clear.

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 only guidance is the prerequisite "Requires a business connection." It gives no guidance on when to use this tool instead of send_message or edit_message_checklist, and no when-not-to-use conditions.

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