composio_connect

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

Beyond the annotations, the description discloses that the tool returns a user-facing link and that the sign-in flow is interactive: the owner must open the URL and complete sign-in before retrying. This is important behavioral context. It does not mention side effects or connection state changes, but the annotations do not contradict the description.

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?

Three terse sentences with no filler: purpose is front-loaded, then the required follow-up workflow, then the exclusions. Every sentence earns its place.

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 a tool with one parameter and no output schema, the description covers the interactive flow and exclusions well. However, it omits valid toolkit values and doesn't explain how to verify the connection after sign-in, so an agent could still invoke it with an unsupported toolkit.

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 only parameter, 'toolkit', has no schema description (0% coverage), and the description never explicitly explains what to pass. The exclusion list implies it selects an integration, but no valid values or examples are given, so an agent may not know what to pass for an allowed app.

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 concrete verb ('Return') and resource ('Composio Connect Link') with a clear purpose: letting the owner sign in to an app. The phrase 'overflow app' is somewhat vague, and it doesn't explicitly differentiate from sibling Composio tools, so it isn't a 5.

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 a clear workflow: open the returned URL, finish sign-in, then retry the original request. It also gives a concrete exclusion list ('Not for Gmail/Calendar/GitHub/Slack/Telegram/Fitbit'). It stops short of naming alternative sibling tools or conditions for when to use composio_status or composio_execute instead.

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