slack_unfurl_link

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

The description discloses routing through /api/tools/invoke and authentication scope (JWT, tenant, company), adding some behavioral context beyond the empty annotations. However, it omits details on permissions, side effects, error handling, or output behavior, which are needed for full 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?

The description is very short (3 sentences) and front-loaded with key routing info. However, the brevity sacrifices completeness, preventing a higher score.

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 lack of annotations, 0% schema coverage, and the complexity of a Slack connector operation, the description is insufficient. It does not specify the expected format of the arguments JSON, output details, or necessary prerequisites, leaving the agent underinformed.

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?

The single parameter 'arguments' has no schema description, but the description explains it is a 'JSON string of arguments for the connector operation,' providing critical meaning. While the expected JSON structure is not detailed, this clarification is valuable and raises the score above baseline.

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 merely restates the tool's name and mentions it's a 'Slack connector operation unfurl_link' without explaining what unfurling a link means or what the tool actually does. It lacks a clear verb and resource description, making it vague and tautological.

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 is provided on when to use this tool versus alternative Slack tools (e.g., slack_post_message, slack_search_messages). The description does not specify context or prerequisites, leaving the agent without direction on appropriate use.

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