slack_app_mention

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

No annotations exist, so the description must disclose behavior. It only mentions routing details (JWT, tenant, company scope) but no behavioral traits like side effects, required permissions, or what happens when invoked. Critical information missing.

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 includes technical routing details that may be irrelevant for selection. It could be more focused on purpose and usage. Information is not front-loaded.

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 tool is a Slack operation, the description lacks essential context about triggers, return values, or effect. Even with an output schema, the behavioral aspects are missing. Incomplete for effective use.

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 coverage is 0%, yet the description merely says 'arguments: JSON string of arguments for the connector operation.' This adds no detail about valid keys or expected structure. The agent cannot know what to pass.

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 states it is a Slack connector operation 'app_mention' but does not explain what 'app_mention' does. The purpose is unclear; it could be sending a mention, listening for mentions, or something else. No verb or action is described.

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 other Slack tools (e.g., slack_post_message, slack_search_messages). No alternatives or context provided. The description does not help the agent decide.

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