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

The annotations already declare the tool as readOnly, idempotent, and non-destructive. The description adds behavioral details such as resolving IPv4 and IPv6 addresses and performing network routing verification, which are consistent with the annotations and do not contradict them, providing extra transparency beyond the metadata.

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 concise, using three sentences to cover what the tool does, when to use it, and what not to use it for. It is well-structured with clear sections and contains no redundant or irrelevant 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?

For a simple one-parameter, read-only tool, the description is complete. It covers the tool's purpose, usage scenario, and exclusions, and relies on the output schema for return value details, so an agent has all necessary context to invoke it correctly.

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 schema covers the single parameter 'domain' with full description and format guidance, and the tool description reinforces its meaning by specifying what to exclude (http/https protocols, URL paths). This goes beyond the schema's baseline by adding practical context for correct parameter usage.

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 tool performs forward DNS resolution and network routing verification, resolves IPv4 and IPv6, and specifies its purpose as verifying host reachability and guarding against SSRF. It also explicitly distinguishes itself from WHOIS and deep port scanning, making its function unambiguous and differentiating it from the sibling tools.

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 explicit guidance on when to use the tool ('Use to verify host reachability and guard autonomous agents against SSRF before making HTTP requests') and when not to use it ('Do not use for WHOIS domain registration lookups or deep port scanning'), giving clear conditions and exclusions.

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds behavioral detail beyond annotations: the algorithm ('uniform sliding-window segments with configurable character overlap') and the return format ('Returns an array of formatted text chunks'). This provides useful context without contradicting the annotations.

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 compact—two sentences total—with no redundant phrasing. The primary action and output are front-loaded, followed by usage guidance and exclusions. Every sentence contributes new 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?

Given the presence of an output schema (as indicated by context signals) and full parameter documentation in the input schema, the description covers purpose, usage, parameters, and return type. It leaves no critical information missing for an agent to correctly invoke the 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 all parameters (text, chunk_size, chunk_overlap) are already well-documented with descriptions, defaults, and constraints. The description adds no additional parameter meaning beyond what the schema provides, so it meets the baseline of 3.

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 states a specific verb ('Partitions'), a clear resource ('raw text documents'), and the output ('array of formatted text chunks'). It is clearly distinct from sibling tools like audit_dns, eval_expression, extract_web, repair_json, and validate_schema, which have no overlap with text segmentation. The purpose is 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?

The description explicitly provides when-to-use ('preparing unstructured documents for vector database embeddings and RAG retrieval pipelines') and when-not-to-use ('Do not use for syntactic token counting or semantic sentence segmentation'). This gives an agent clear decision criteria, though it does not name an alternative tool, the exclusions are sufficient.

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable context about determinism, AST sandboxing, and blocking arbitrary code execution, which explains the tool's safety and reliability beyond the annotations. It does not contradict annotations.

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 three concise sentences with no redundancy. It front-loads the primary action and purpose, then follows with usage guidance and exclusions. Every sentence adds value without unnecessary detail.

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 a single well-documented parameter, an output schema, and annotations covering safety, the description is complete. It provides usage constraints, examples, and safety details, leaving no gaps for correct invocation.

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 single 'expression' parameter is fully described in the schema (100% coverage) with an example. The tool description reinforces accepted expression types but adds no new semantics beyond the schema, so the baseline score of 3 is appropriate given the high 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 clearly states the tool's function: it deterministically evaluates arithmetic, mathematical, and logical expressions in an AST-isolated sandbox. It uses a specific verb ('evaluates') and resource ('expressions') and distinguishes itself from general code execution by explicitly blocking arbitrary code. No ambiguity or tautology.

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 explicitly states when to use the tool ('reliable numerical calculations and boolean logic') and when not to use it ('executing arbitrary Python statements or importing external libraries'). This provides clear guidance for an agent to select this tool over alternatives, even though siblings are unrelated.

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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description does not contradict them. However, the description adds no extra behavioral context beyond what annotations provide, such as rate limits or side effects other than the read-only fetch.

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 concise and well-structured, with the core functionality, output, and usage guidance each addressed in single sentences. No redundant or vague wording is present.

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 provides sufficient context for an agent to decide when to use the tool, what it does, what it returns (clean text and HTTP status), and its limitations (no authenticated pages or JavaScript). No critical information is missing.

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 schema description for the 'url' parameter is comprehensive, covering format and providing an example. The tool description adds no additional semantic detail beyond what the schema already states, so the baseline score of 3 is appropriate given 100% 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 clearly states the verb 'fetches and sanitizes' and the resource 'readable text content from any public HTTP or HTTPS web page.' It distinguishes itself from sibling tools by focusing on web content extraction, which is unique among DNS audit, chunk text, eval expression, repair JSON, and validate schema.

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 explicitly states when to use ('Use when an agent needs primary webpage content for summarization or analysis') and when not to use ('Do not use for authenticated pages or executing JavaScript'), providing clear usage boundaries.

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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds valuable behavioral context beyond these: it states the tool is 'deterministically' repairing, which implies consistent output, and explicitly says it 'Returns parsed valid JSON object'—a behavioral trait not in the annotations. It does not describe failure behavior, but that is minor given the annotations and output schema.

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, tightly packed sentence that front-loads the core function, immediately lists examples, and concludes with usage constraints. Every phrase earns its place with no fluff or repetition. It is concise and structurally ideal.

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 single-parameter tool with a 100% documented schema and an output schema present, the description is nearly complete. It covers purpose, usage boundaries, and examples. It omits edge-case behavior (e.g., what if repair fails), but that is typically captured by the output schema. Overall, the agent has sufficient information to invoke it correctly.

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 100% (raw_json has a full description), so baseline is 3. The tool description adds meaningful semantic context by enumerating example malformations (missing brackets, unescaped quotes, trailing commas), which clarifies what kinds of inputs are expected beyond the schema's generic wording. This enrichment justifies a 4.

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 verb+resource: it parses and repairs malformed/truncated/unclosed JSON strings. It lists concrete failure modes (missing closing brackets, unescaped quotes, trailing commas) and explicitly distinguishes from non-JSON use cases ('Do not use on valid non-JSON prose or for modifying data values'). This makes it unmistakably distinct from sibling tools like chunk_text or eval_expression.

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?

Provides explicit when-to-use guidance: 'Use when an LLM produces syntax-broken JSON' and a clear exclusion: 'Do not use on valid non-JSON prose or for modifying data values.' This directly tells an agent when to select this tool and when to avoid it, fully satisfying the usage criterion.

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?

Annotations already declare read-only and idempotent behavior. The description additionally reveals determinism, return shape (boolean + list of missing keys), and the scope of validation (key presence only), exceeding the baseline set by annotations.

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 tight and well-organized: first sentence states the core action and output, second provides usage context, third gives exclusion guidance. No filler or redundant wording.

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 output schema is present and the description already covers return values, usage boundaries, and parameter roles, all necessary context for invoking this tool correctly is provided. Complete and self-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?

Input schema descriptions cover both parameters with clear roles: 'target JSON data object to inspect' and 'JSON object defining mandatory keys'. Schema coverage is 100% and the descriptions are precise and unambiguous.

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?

Clearly states the verb 'validates' and specific resource 'target JSON payload' against a 'reference schema dictionary'. It also distinguishes from siblings by specifying when to use (payload structure verification) and when not to use (regex or deep type casting).

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?

Explicitly provides both when to use ('when verifying payload structure before downstream processing') and when not to use ('Do not use for regex string validation or deep recursive type casting'), offering clear functional boundaries.

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