Server Quality Checklist

Tool Scores

• waitC
  2.4/5.0
  Behavior2/5

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

  No annotations exist, so the description must carry the burden of disclosing behavior. It only says 'Wait' without explaining whether it blocks, how timeouts are handled, what happens on timeout, or whether it can wait for multiple condition types. The lack of any behavioral detail leaves the agent guessing about side effects and execution semantics.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness2/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single vague sentence that is brief but not effective. It lacks front-loaded specifics and does not earn its place, as 'various conditions' adds minimal value. A concise description should still convey key details; this one is under-specified.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool has 3 parameters, an enum type, and no output schema, the description is far from complete. It does not explain the meaning of the three wait types, expected return values, or error behavior. The sibling context suggests a browser automation tool but does not compensate for the missing information.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, with each parameter (type, value, timeout) having a clear description. The tool description adds no extra meaning beyond 'various conditions', so it neither improves nor harms parameter understanding. Baseline 3 is appropriate because the schema handles the semantics.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose3/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description 'Wait for various conditions' provides a clear verb and object but remains vague about what specific conditions are supported. It does not mention the selector, navigation, or timeout types defined in the schema, nor does it distinguish itself well from sibling tools. This is not a tautology but lacks the specificity expected for a useful purpose statement.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description gives no guidance on when to use this tool versus alternatives like click or navigate. It does not specify scenarios, prerequisites, or any exclusions. With no context on usage, the agent is left to infer from the schema and sibling names.

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

• navigateC
  2.6/5.0
  Behavior1/5

  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. It only states the action and gives no information about side effects, page state changes, wait behavior, or error handling. The waitUntil parameter is not mentioned in the description.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness3/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is appropriately brief and front-loaded, but it is under-specified rather than effectively concise. It lacks any structural elements like examples or formatting that would aid understanding.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's moderate complexity, two parameters, and lack of annotations or output schema, the description is incomplete. It does not explain navigation completion, return value, or how this tool fits into a browser automation session.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema fully documents both parameters with descriptions, so the baseline is 3. The description adds no additional semantic meaning beyond what the schema already provides.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description 'Navigate to a URL' clearly states the tool's purpose with a specific verb and resource. However, it does not explicitly distinguish navigate from sibling tools like click or get_content, so it lacks sibling differentiation.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides no guidance on when to use navigate versus alternatives. It does not mention prerequisites, typical scenarios, or when this tool is preferred over other browser actions, leaving the agent without usage context.

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

• clickC
  2.9/5.0
  Behavior2/5

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

  Without annotations, the description carries full responsibility for disclosing behavioral traits. It only says 'Click on an element' and does not mention side effects, waiting behavior, error handling, or whether it clicks the first matching element. This is a significant gap for a state-changing action.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, clear sentence with no redundant words. It is appropriately concise for the tool's simplicity, ensuring every word contributes to understanding the tool's purpose.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Even though the tool is simple with well-documented parameters, the absence of annotations means the description must provide more context. It lacks any behavioral notes, error behavior, or usage guidance, making it incomplete for an agent that needs to invoke it correctly in varied scenarios.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema already provides 100% coverage with descriptions for both 'selector' and 'waitForNavigation', so the baseline is 3. The description adds no additional meaning beyond the schema, making it neither better nor worse.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description 'Click on an element' clearly states the action and object, making it distinct from sibling tools like type or navigate. However, it lacks explicit mention of using a CSS selector or the option to wait for navigation, which are covered in the schema.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No guidance is provided on when to use this tool versus alternatives such as type or navigate. The description does not indicate any exclusions or prerequisites, leaving the agent without direction on selecting this tool over siblings.

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

• solve_captchaC
  2.9/5.0
  Behavior2/5

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

  With no annotations provided, the description carries the full burden of disclosing behavioral traits. It mentions 'if supported' but does not explain what unsupported types mean, whether the tool may fail, or any side effects. The hedged phrasing hints at uncertainty but offers no concrete details.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single concise sentence with no wasted words. It is appropriately brief, though it could sacrifice some brevity for more useful detail.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  The tool is simple with one enum parameter, but the description still leaves key questions unanswered: which CAPTCHA types are actually supported, what happens if a type is unsupported, and what the return value indicates. Without an output schema, the description should explain these aspects but does not.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 100% with the 'type' parameter already having an enum and description. The description adds no additional semantic value, but since the schema handles parameter documentation fully, the baseline score of 3 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose4/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool solves CAPTCHAs, which is a distinct resource from the sibling browser automation tools. However, the hedging word 'Attempt' and the vague 'if supported' qualify the action, making the purpose less definitive than it could be.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or context. The reader is left to infer that it should be used when encountering a CAPTCHA.

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

• typeB
  3.2/5.0
  Behavior2/5

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

  No annotations are present, so the description carries the full burden. It doesn't disclose whether it clears existing content, simulates individual keystrokes, or requires the element to be focused. The delay parameter is mentioned only in the schema, not in the description.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single sentence of six words, front-loading the core action and target. Every word contributes value, with no redundancy or filler.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a mutation tool with no annotations and no output schema, the description is too thin. It doesn't address behavior like overwriting vs. appending, event triggering, or error conditions. The schema documents parameters but not the operational context.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, so the parameters are already well-documented. The description adds no additional meaning to selector, text, or delay beyond what the schema provides, so the baseline score of 3 applies.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description 'Type text into an input field' clearly identifies the action (type) and the resource (input field). It distinguishes from siblings like click, get_content, and navigate because it's the only tool for entering text.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No guidance on when to use this tool versus alternatives. It doesn't mention that it's for filling form inputs or that it shouldn't be used for clicking or navigating. No exclusions or prerequisites are provided.

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

• browser_initB
  3.4/5.0
  Behavior2/5

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

  No annotations are provided, so the description must carry the behavioral transparency burden. It mentions 'anti-detection features' and 'automatic Chrome path detection,' but does not disclose side effects, idempotency, resource cleanup, or what happens on repeated calls. This is insufficient for an initialization tool.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single concise sentence that front-loads the primary action and key differentiators. Every word earns its place with no redundancy.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a complex tool with 7 parameters, nested objects, and no output schema, the description is thin. It does not explain return values, the need to call browser_close, or the lifecycle implications of initialization. The schema provides parameter details, but the description lacks broader context for a task-level agent.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 100% with detailed parameter descriptions, so the baseline is 3. The description adds marginal context (auto path detection relates to chromePath), but does not substantively add meaning beyond the schema.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description uses a specific verb 'Initialize' and resource 'browser instance', and distinguishes itself from sibling tools by highlighting anti-detection features and automatic Chrome path detection. This clearly states what the tool does and sets it apart from navigation and automation tools.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies this is a setup step for browser automation, but does not explicitly state when to call it relative to other tools or provide exclusions/alternatives. The context suggests it should be used first, but the description itself lacks explicit usage guidance.

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

• find_selectorB
  3.4/5.0
  Behavior2/5

  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 does not disclose the return format, what happens on no match or multiple matches, or whether it performs a read-only DOM search. The behavior is only vaguely implied.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, compact sentence that efficiently conveys the core function without any redundant words. It earns its place by adding specific detail beyond the tool name.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  With no output schema and no annotations, the description should clarify return values and edge-case behavior. It does not state whether it returns a string, an array, or throws on missing text, leaving significant gaps for autonomous use.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema covers 100% of the parameters with clear descriptions. The tool description adds no extra meaning beyond the schema, so it meets the baseline but does not enhance parameter understanding.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description uses a specific verb and resource ('Find CSS selector for element containing specific text'), making it clear what the tool does. It also distinguishes itself from sibling tools like click or navigate by focusing on selector discovery.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The usage is implied by the purpose: use this tool when you need a CSS selector for an element by its text. However, there is no explicit guidance on when not to use it or how it compares to alternatives.

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

• save_content_as_markdownB
  3.4/5.0
  Behavior2/5

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

  With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It states the tool saves content to a file, but it does not mention side effects such as overwriting existing files, permission requirements, or error behavior. The conversion to markdown is implied but not detailed, leaving significant gaps in transparency.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, clear sentence that front-loads the primary purpose without any redundancy or extraneous words. Every word contributes meaning, making it highly concise.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool has four parameters, a nested object, no output schema, and no annotations, the one-sentence description is insufficient. It fails to explain what happens after saving (e.g., return values, file overwrite behavior), any prerequisites, or potential side effects, leaving the agent without enough context to use the tool safely and effectively.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema provides 100% coverage with detailed descriptions for all four parameters, including nested formatOptions. The description adds no additional parameter semantics, so the baseline score of 3 applies as the schema already carries the explanatory burden.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool's function with specific verbs ('extract' and 'save') and identifies both the resource ('page content') and the output ('formatted markdown file'). It distinguishes itself from sibling tools like get_content, which focuses solely on retrieval without saving.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies usage (when you need to save content as markdown), but it does not explicitly state when to use this tool versus alternatives like get_content, nor does it provide exclusions or alternative tool pointers. This leaves usage guidance to be inferred from the name and context.

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

• random_scrollA
  3.5/5.0
  Behavior2/5

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

  With no annotations, the description carries full responsibility for disclosing behavior. While 'natural timing' hints at human-like delays, it does not explain whether scrolling is continuous, random in direction, or how long it lasts. Key behavioral traits like potential side effects or interruptibility are absent.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, concise sentence with no filler. It is front-loaded with the action ('Perform random scrolling') and the qualifier ('with natural timing') adds value without bloat. Every word earns its place.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a simple tool with no parameters and no output schema, the description covers the basic purpose but omits usage context and behavioral details. It is minimally viable but lacks the richness expected for a browser automation tool, especially with no annotations to fill gaps.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The tool has zero parameters, so the schema is fully covered trivially. The description does not need to add parameter details. A baseline of 4 is appropriate because there is nothing to clarify beyond the schema.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool performs random scrolling with natural timing, using a specific verb and resource. It distinguishes itself from siblings like 'navigate' and 'click' by focusing on scroll behavior. The purpose is unambiguous in the browser automation context.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No guidance is provided on when to use this tool versus alternatives. There is no mention of scenarios where random scrolling is beneficial, such as mimicking human behavior, nor any exclusions or alternatives. The description only states what it does without contextual use cases.

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

• browser_closeA
  3.6/5.0
  Behavior2/5

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

  No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without noting side effects like session termination, unsaved data loss, or irreversibility. This is minimal but not misleading.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single sentence that is direct and front-loaded with the verb 'close'. There is no wasted content, making it highly concise.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a simple close action, the description is adequate, but it could note that it permanently ends the browser session. The lack of behavioral caveats slightly reduces completeness, though no output schema exists to explain return values.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The tool accepts zero parameters, and the input schema confirms an empty object. Since there are no parameters, the description does not need to add parameter details, and the baseline for 0 params is 4.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description uses a specific verb 'close' and resource 'browser instance', clearly distinguishing it from sibling tools like browser_init and navigate. It unambiguously states the tool's function.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No guidance is provided on when to use this tool, such as as a cleanup step after automation completes. There is no mention of alternatives, prerequisites, or exclusions.

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

• get_contentA
  4/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries the behavioral burden. It states that this method is 'more reliable than screenshots', which is a behavioral comparison, but it does not disclose limitations such as whether it waits for page load or what happens when a selector is not found. This leaves some behavioral uncertainty.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, front-loaded sentence that immediately conveys the recommendation and purpose. Every word earns its place, with no redundant details.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's low complexity (2 params, no output schema, no annotations), the description covers the core purpose and usage context adequately. However, it could briefly mention what the return format looks like (e.g., raw HTML or plain text) to be more complete, so a slight gap exists.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema fully describes both parameters (type with enum/default, selector with description), so schema coverage is 100%. The description adds no extra context about how these parameters affect the output, so it does not exceed the baseline.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description explicitly states the tool retrieves page content (HTML or text), using a clear verb ('get') and resource ('page content'). It also distinguishes itself from screenshots, which are a common alternative for capturing page state, thereby clarifying its unique value.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description marks itself as 'Recommended' and specifies that it is intended for 'content analysis and navigation tasks', giving clear when-to-use guidance. However, it does not mention sibling tools like save_content_as_markdown or find_selector as alternatives, so exclusions are not fully addressed.

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