check_medium_session

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. The term 'check' implies a read-only operation, and 'appears to be signed in' hints at heuristic behavior, but it does not specify return type, side effects (e.g., whether a browser is opened), or what happens if not signed in. The description gives basic transparency but leaves significant behavioral details unstated.

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, concise sentence that front-loads the main action and resource. It contains no filler or redundant information, making it highly efficient and easy to parse.

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 simple no-parameter tool with no output schema, the description adequately communicates the core function. However, it falls short of specifying the exact return value (e.g., boolean or status string) or any potential side effects, which would enhance completeness. Given the tool's simplicity, the description is nearly sufficient but not fully complete.

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 has zero parameters, and the input schema is an empty object. The baseline for 0 parameters is 4, and the description correctly focuses solely on the tool's purpose without needing to document parameter semantics. No additional parameter explanation is required.

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 specifies the verb 'Check' and the target resource 'dedicated Medium browser profile' for session status. It distinguishes itself from sibling tools like login_to_medium (which performs login) and get_medium_article (which fetches content), making its purpose unambiguous.

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?

Usage context is implied: this is a status check to determine if the Medium session is active, likely before login or to verify authentication. However, it does not explicitly state when to use it versus alternatives or provide any preconditions, so guidance is only implicit.

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