CSG Portal 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. It discloses key behavioral traits: it opens a browser for secure authentication and ensures credentials are not exposed in Claude. This covers safety and interaction method, though it lacks details on session persistence or error handling.

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 front-loaded with the core purpose in the first sentence, followed by a clarifying detail about browser interaction and security. Every sentence adds value without redundancy, making it efficient and well-structured.

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 no annotations and no output schema, the description adequately covers the tool's purpose and key behavior (browser-based auth, credential safety). However, it doesn't address potential outcomes like success/failure states or session management, leaving some gaps for a login tool.

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 100%, so the schema already documents the optional 'userEmail' parameter. The description doesn't add meaning beyond the schema, such as explaining why email is used for 'session isolation and identification'. Baseline 3 is appropriate as the schema handles parameter documentation.

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 action ('Log in') and target ('CSG Veracross portal'), specifying it opens a browser for authentication. It distinguishes from siblings like 'check_authentication' by focusing on initiating login. However, it doesn't explicitly differentiate from 'set_default_user' which might relate to user setup.

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 for authentication when needed, but doesn't explicitly state when to use this tool versus alternatives like 'check_authentication' (to verify status) or 'clear_credentials' (to remove stored data). No guidance on prerequisites or exclusions is provided.

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