wetrack_set_token

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

No annotations are provided, so the description carries the full burden. It reveals important behavioral details: the token is stored in-memory, applies to all subsequent calls, and is session-scoped only. It also clarifies that Bearer <token> is added automatically, which helps the agent understand side effects.

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, front-loaded with the core purpose, and organized into short useful sections. Every sentence adds information: what it does, when to use it, what the parameter is, and what happens afterward.

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 one-parameter session-setup tool, the description is largely complete: purpose, timing, parameter semantics, and session-only storage are all covered. It could optionally mention that setting a new token replaces any existing session token, but that is a minor gap.

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 schema only defines 'token' as a required string with 0% description coverage. The description compensates by explaining it is 'The JWT Bearer token string from your WeTrack session,' and that all subsequent calls will use it as Bearer <token>. This is meaningful guidance beyond the schema.

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 verb and resource: 'Manually set a JWT token for all subsequent WeTrack API calls.' This is distinct from sibling tools like wetrack_sign_in or wetrack_get_microsoft_signin_url, which handle OAuth login rather than manual token injection.

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 gives explicit usage context: 'Use this after completing Microsoft OAuth login in a browser to store your token in the MCP server session.' It does not explicitly name alternatives or when-not-to-use cases, but the intended workflow is clear.

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