connect

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

Annotations cover the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), and the description adds meaningful context: it opens a browser (a side effect the agent must expect), it is interactive, and credentials must not be supplied. It stops short of describing session persistence or what state results after login.

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?

Two short sentences, the primary purpose front-loaded and the critical safety constraint immediately after. No wasted words.

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?

With no parameters and no output schema, little more is needed. The description could note what to do after connecting (e.g., check connection_status) to fully close the loop, but the core action and its constraint are covered.

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 tool takes zero parameters, so there is no parameter documentation burden. The note that credentials should never be passed is a useful clarification given the empty schema, though nothing else needs explaining.

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?

States a specific action (open a private browser) on a named resource (Gradescope session) and clarifies the mode (interactive login). This clearly distinguishes it from siblings like connection_status (which presumably reports state) and sync (which performs data operations).

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 when to use it (interactive login) but never explicitly says when to call it versus connection_status, nor states prerequisites such as needing to run this before sync. The one explicit constraint ('never pass credentials') is a usage rule but not a routing rule.

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