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.

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

With no annotations provided, the description carries the burden of behavioral disclosure. It correctly identifies the operation as read-only and mentions the output format, but it does not disclose behavior on invalid URLs, paywalled content, or session expiry. The mention of the persisted session adds useful context but not full transparency.

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, front-loaded sentence that conveys the action, resource, session dependency, and output format without any 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?

Given the tool's simplicity (one parameter, no output schema) and the lack of annotations, the description covers the core purpose and output format. It does not mention error cases or interactions with sibling tools, but for a straightforward read operation, this level of completeness is sufficient.

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 already has 100% coverage with a clear description of the 'url' parameter. The tool description adds the context of reading and returning Markdown, but does not add significant new meaning to the parameter itself. Baseline of 3 is appropriate given the schema coverage.

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 uses the specific verb 'Read' with a clear resource ('a Medium article') and states the output format ('return Markdown'). It clearly distinguishes from sibling tools like search_medium (finding articles) and check_medium_session (session status).

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 provides clear context by specifying it uses the 'locally persisted Medium browser session', implying a prerequisite for the tool to work. However, it stops short of explicitly stating when to use this tool versus alternatives or 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.

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly explains that the tool opens a dedicated persistent Microsoft Edge profile, requires manual user action for Google sign-in, and occurs in a visible browser window. This gives the agent a good picture of the interactive, persistent nature of the login. It could add what happens after sign-in (e.g., whether the tool waits or returns success), but this is a minor omission.

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 sentences with no redundant phrasing. The description is front-loaded with the core action and immediately provides key behavioral context (dedicated profile, manual sign-in, visible window). Every word earns its place.

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, the description covers the essential behavior and context well. It lacks information about return values or whether the tool blocks until sign-in is complete, but given the absence of an output schema and the tool's simplicity, it is reasonably complete. An explicit note about not being headless would add completeness, but the visible-browser detail already implies this.

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, so the baseline for this dimension is 4. The description appropriately does not need to add parameter-level detail because there are none.

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 uses a specific verb (Open) and resource (Medium's sign-in page in a dedicated persistent Microsoft Edge profile), making it clear this is the login/authentication tool. It clearly differentiates from sibling tools (check_medium_session, get_medium_article, search_medium) by focusing on sign-in 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 this is the initial manual login step but does not explicitly state when to use it versus alternatives. It would benefit from saying 'Use this before check_medium_session if the session is not already active' or 'Use this once to establish a persistent login.' No exclusions or alternative tool mentions are provided.

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

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

No annotations are provided, so the description must disclose behavior. It mentions the return fields, which is useful, but it does not disclose whether authentication is required, any rate limits, or side effects. The presence of sibling login_to_medium suggests authentication might be relevant, but this is not addressed.

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 action and output, with no redundant information.

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?

The description is adequate for a simple search tool, covering the action and output fields, but it lacks information about authentication requirements and parameter semantics (especially limit), making it incomplete for a tool with no output schema and no annotations.

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 coverage is 50%—the 'query' parameter has a description, but 'limit' does not. The tool description does not explain the limit parameter's meaning or any parameter-specific behavior, so it does not compensate for the missing schema 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 a specific action ('Search Medium') and the expected output fields (titles, URLs, authors, excerpts). This distinguishes it from the sibling tools like get_medium_article, which fetches a specific article.

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 does not explicitly state when to use this tool over alternatives, nor does it mention exclusions or prerequisites. It implies a search use-case but lacks explicit guidance referencing sibling tools such as get_medium_article or login_to_medium.

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