slack_team_info

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

With no annotations, the description must disclose behavioral traits. It mentions routing via /api/tools/invoke with authentication context, but fails to state whether the operation is read-only, its side effects, performance impact, or response format. The output schema exists but is not described.

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 concise (two sentences) but wastes the first sentence restating the name. It is front-loaded with the name repetition and lacks substantive content, though it avoids verbosity.

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 complexity of retrieving team info, the description is severely incomplete. It does not explain what data is returned (though an output schema exists), what arguments are needed, or how errors are handled. The agent lacks essential context to use this tool effectively.

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 'arguments' parameter has 0% schema description coverage, and the description only repeats that it is a JSON string of arguments without explaining expected keys (e.g., team ID) or structure. This provides no useful guidance for constructing the parameter value.

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 name as 'Slack connector operation `team_info`' without specifying what team information is retrieved (e.g., team name, members, details). The routing context does not clarify the core purpose, leaving the agent uncertain about the tool's exact function.

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 other Slack tools like slack_list_channels or slack_list_users. There are no usage examples, prerequisites, or alternative recommendations, making it impossible for the agent to choose appropriately.

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