send_group_attachment

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

No annotations provided, so description carries the burden. It discloses that files must exist locally, non-existent paths return an error, and view_once does not apply to documents. However, it does not mention rate limits, size limits, or what happens if group_id is invalid. Additional behavioral details could improve transparency.

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?

Description is concise with 5 sentences, front-loaded with key purpose and functionality. Every sentence adds value without redundancy. Efficient and well-structured.

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?

No output schema, but description covers the main aspects of the tool: supported file types, delivery method, view_once behavior, and parameter usage. Missing details on failure modes or size limits, but adequate for a send operation with 5 parameters. Could mention return values briefly.

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 100%, so baseline is 3. The description adds value by clarifying that view_once does not apply to document types (not in schema) and explaining the path vs paths distinction. This extra context justifies a higher score.

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 the tool sends files (photos, videos, documents, audio) to a Signal group in a single message. It explicitly distinguishes from siblings by directing to use send_attachment for direct messages and send_group_message for text-only messages, providing a specific verb and resource.

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?

Provides explicit when to use: sharing files with a group chat. Also gives when not to use: direct messages or text-only. Mentions using list_groups to obtain group_id. Does not explicitly clarify when to use single path vs multiple paths, but the description and schema imply both are valid.

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