Compliance Tools

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

The description adds meaningful behavioral context beyond annotations: it is deterministic, robots-aware, uses no LLMs, and provides no legal verdicts. It also discloses the pricing model. This is valuable transparency, though it does not clarify side effects despite readOnlyHint=false.

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 short sentences: purpose, behavioral traits, and pricing. It is front-loaded with the core function and contains no filler. Every sentence 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?

With no output schema, the description does not explain what the output looks like (e.g., lead lists, evidence rows). It gives a clear high-level purpose and behavioral constraints, but the lack of output format and minimal usage guidance leaves some gaps. Still, the tool is conceptually simple and the schema covers inputs thoroughly.

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 the schema already documents all parameters well. The description itself adds no parameter-specific meaning, which is acceptable given the schema's richness. Baseline 3 is appropriate.

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 ('scanner') and resource ('submitted URL'), and defines the scope as 'accessibility and privacy exposure signals.' It clearly differentiates from the sibling tool 'eu-ai-act-transparency-lead-scanner' by topic. The acronym 'BYOD' is ambiguous, but the overall purpose is unmistakable.

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 usage for auditing a URL's accessibility/privacy compliance, but it does not explicitly say when to use this tool versus the sibling AI Act scanner. No exclusions or alternatives are mentioned, leaving the agent to infer appropriate selection from the name/description alone.

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 provide readOnlyHint=false and destructiveHint=false. The description adds valuable behavioral context: deterministic processing, robots-aware crawling, no LLM involvement, no legal verdicts, and a per-call cost with payment method. This goes beyond the structured annotations without contradicting them.

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, well-structured sentence. It front-loads the core purpose, then adds key behavioral constraints and pricing in a compact list. No wasted words; every phrase contributes to understanding the tool.

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 tool has 6 parameters and no output schema, yet the description does not explain what the returned rows ('useful rows') contain or what a 'lead' means. It covers purpose and constraints but lacks details on output format, which is significant given the absence of an output schema. The detailLevel parameter hints at selectors and excerpts, but the description itself does not clarify the return value.

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% with each parameter already explained. The description does not need to add parameter-specific details, and it doesn't. Baseline of 3 is appropriate as the schema carries the semantic load.

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 is a 'BYOD compliance scanner for observed AI transparency signals on a submitted URL.' This specifies the verb (scanner), resource (AI transparency signals), and distinguishes it from the sibling accessibility/privacy scanner. Additional qualifiers like 'no legal verdicts' further clarify its scope.

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 the tool (for deterministic, robots-aware AI transparency scanning) and what it avoids (LLMs, legal verdicts). However, it does not explicitly contrast with sibling tools or state when not to use it, leaving usage context mostly implied.

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 mark the tool as read-only and non-destructive. The description adds that it is 'Free' and that it should be called first when no wallet is ready, providing extra behavioral context beyond 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?

Two sentences, front-loaded with the essential 'Free' label and a clear statement of function, followed by a concise usage hint. No filler or redundancy.

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 zero-parameter tool with no output schema, the description fully covers the purpose, the returned information (price, payTo address, network), and the recommended usage context, making it complete for the agent.

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 0 parameters, so the schema is fully covered and there is nothing to explain. The baseline for a zero-parameter tool is 4, and the description appropriately focuses on output contents instead.

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?

Specific verb 'list', resource 'paid tools in the compliance-tools bundle', and details (price, payTo address, network) clearly define what the tool does and distinguish it from the sibling scanner 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?

Explicitly says 'Call this first if you don't have a wallet ready yet,' giving a clear when-to-use context. However, it does not mention when not to use it or compare directly to alternative tools.

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