rtm_start

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

The description only says 'Start a Real Time Messaging session' with no additional behavioral details. Since no annotations are provided, the description carries full burden but fails to disclose any side effects, authentication needs, rate limits, or state changes.

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?

One efficient sentence covering the core purpose and deprecation. Every word earns its place; no fluff.

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?

Despite having 7 parameters, no output schema description, and zero schema descriptions, the description provides no explanation of parameters or return values. The tool is deprecated, but the description is too sparse for an agent to use correctly even if needed.

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 description coverage is 0%, and the description does not mention any of the 7 parameters (e.g., batch_presence_aware, include_locale). The agent receives no guidance on how these booleans affect the RTM session.

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?

Clearly states the tool starts a Real Time Messaging session and explicitly marks it as deprecated with a direct replacement (rtm.connect). The verb 'Start' and resource are specific.

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 explicit guidance: 'deprecated, use rtm.connect'. This tells the agent not to use this tool and directs to an alternative, which is ideal usage guidance.

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