TeamSnap MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the action ('Disconnect and clear stored credentials'), which implies a destructive operation that removes authentication data. However, it lacks details on effects like whether this logs out all sessions, requires re-authentication for subsequent calls, or has any side effects on other tools.

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 a single, efficient sentence that front-loads the key action ('Disconnect from TeamSnap') and adds necessary context ('clear stored credentials'). There is zero waste, and every word earns its place in conveying the tool's purpose.

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 tool's complexity (simple logout with 0 parameters) and no annotations or output schema, the description is minimally complete. It states what the tool does but lacks details on behavioral aspects like confirmation prompts, error handling, or what happens post-logout. For a destructive operation, more context would be helpful.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate. Baseline is 4 for 0 parameters, as it compensates by not introducing unnecessary information.

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 clearly states the specific action ('Disconnect from TeamSnap') and the resource affected ('stored credentials'), distinguishing it from sibling tools like teamsnap_auth or teamsnap_auth_status which handle authentication rather than disconnection. It uses precise verbs and identifies exactly what gets cleared.

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?

The description implies usage context by mentioning 'clear stored credentials,' suggesting it should be used when ending a session or revoking access. However, it does not explicitly state when to use this tool versus alternatives like teamsnap_auth_status for checking auth state, or provide exclusions for when not to use it.

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