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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds one useful behavioral note — output is scoped to the linked Market Brew account — but says nothing about the schedule's format or coverage.

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 short sentences, no filler, with the usage condition front-loaded. It is efficient, though the second sentence is the only substantive content.

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 read tool, the description leaves both the purpose ('explicit' schedule vs. other crawl data) and the parameter semantics unresolved, and there is no output schema to compensate.

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 0% and the single 'website' parameter accepts either a string or a number with no explanation. The description adds nothing about whether this is a domain, URL, or internal ID, leaving the parameter ambiguous.

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 essentially restates the title: 'Use this when the user asks to get explicit crawl schedule.' It names a resource (crawl schedule) but 'explicit' is undefined and it offers no differentiation from siblings like get_crawl_metrics, get_deep_crawl_seed, or list_deep_crawl_seeds.

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 trigger condition is circular — 'use this when the user asks to get explicit crawl schedule' — which tells the agent nothing beyond the tool name. No alternatives, prerequisites, or when-not-to-use conditions are named.

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