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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful content context (what data comes back), but says nothing about date-range behavior, the range_preset/start_date/end_date interaction, pagination, or rate limits.

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, purpose front-loaded, then a compact enumeration of returned artifacts. No filler or redundancy; could be slightly tighter but is well structured for its length.

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 useful work listing the five returned data shapes. However, for a 5-parameter tool at 20% schema coverage it leaves the date-range and preset semantics entirely unexplained, which is a real gap 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?

Five parameters with only 20% schema description coverage — brand_id, start_date, end_date, and range_preset are undocumented in the schema, and the description explains none of them. The description's listed returns do not compensate for the parameter gap, so it fails to do the burden-carrying that low coverage requires.

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+resource ('Get the crawler Access tab data') plus an enumeration of returned artifacts (findings, bot access matrix, robots.txt, llms.txt, submit-to-search status) that meaningfully distinguishes it from crawler siblings like get_crawler_submit_status or get_crawler_overview. It does not, however, name any alternative tool, so differentiation is implicit rather than explicit.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no routing to alternatives despite five crawler-related siblings (get_crawler_detail, get_crawler_live, get_crawler_overview, get_crawler_pages, get_crawler_submit_status). The 'Access tab' framing implies a dashboard context but never states it as a selection rule.

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