start_agent_adoption_scan

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

Annotations already indicate non-read and open-world behavior. Description adds async nature, immediate scanId return, record creation, and typical timing, providing rich behavioral context.

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 key information, no 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 an async scan tool with one parameter and no output schema, the description provides all necessary context: what it does, how to retrieve results, and expected timing.

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?

Only one parameter 'domain' with schema description 'Domain to scan, e.g. example.com'. Schema coverage is 100%, and description adds context about any domain and scope of checks, adding value beyond schema.

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 it starts an async Agent-Adoption Check on any domain, specifying 25 checks across discoverability, access control, content readability, and agent endpoints. Differentiates from siblings like get_agent_adoption_scan and check_ai_crawlers.

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 mentions to poll with get_agent_adoption_scan, and gives typical completion time. Lacks explicit 'when not to use' but provides clear context for usage.

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