slack_team_info

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

Annotations already carry readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the read-only safety profile is covered. The description adds some useful context beyond annotations: the governed-connector routing constraint and the fact that 'effect' must be 'read' and is verified by Spring. It does not contradict the annotations (approval_ref talk of 'resuming a write' is generic boilerplate), but it adds only modest behavioral value beyond the structured hints.

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 compact and well-organized: a header line, a routing constraint, then a bullet-style Args list covering all seven parameters. The opening line is partially redundant with the tool name, but the rest of the text is functional and free of filler, keeping the total length appropriate for a wrapper tool with seven parameters.

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?

An output schema exists, so return-value documentation is not required, and the description does cover all parameters (compensating for the schema's lack of descriptions). However, it never explains what 'arguments' should contain for a team_info call, which parameters are actually needed to satisfy the governed routing, or what the outcome of the call is, leaving gaps for an agent trying to invoke it correctly.

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?

With 0% schema description coverage, the description is the only source of parameter meaning, and it provides a one-line gloss for all seven parameters (e.g., project_id: 'Authenticated Project UUID', connector_account_ref: 'Project-bound connector account alias'). The definitions are terse and `arguments` remains opaque ('JSON string of arguments'), but the description compensates substantially where the schema offers nothing.

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 only restates the tool identity ('Slack connector operation team_info (platform tool slack.team_info)') and a routing constraint, without ever stating that this retrieves Slack team/workspace information. It reads as a near-tautology: an agent learns the operation is called team_info but not what it does or what it returns.

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?

There is no guidance on when to use this tool versus alternatives such as slack_list_channels, slack_users_info, or other slack_* tools. The routing sentence ('Routes only through the exact project/account governed connector authority') is a governance constraint, not usage guidance, and no when-to-use/when-not-to-use context is provided.

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