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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description contributes the notion of a 'summary' (an aggregated view) over submission statuses, but says nothing about pagination, result limits, or how the url/status/date filters behave. With annotations carrying the main load, a 3 is fair.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though for a 7-parameter tool the brevity borders on under-specification rather than pure conciseness.

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 7 parameters, 14% schema coverage, and no output schema, the description leaves an agent unable to construct a correct call — the filtering semantics and date/preset interaction are undocumented. It is far too thin for the tool's complexity.

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 only 14% across 7 parameters, so the description must compensate — and it does not. It never explains that 'urls' accepts one or more crawler URLs, what the pending/success/failed status filter means, how start_date/end_date interact with range_preset (default 30d), or the purpose of brand_id and user_intent.

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?

States a specific verb (Get) and resource (submit-to-search status and summary for crawler URLs), which is enough to distinguish it from the write-side sibling submit_crawler_to_search. It does not explicitly differentiate itself from the other crawler tools (get_crawler_overview, get_crawler_pages, etc.), so it stops short of a 5.

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?

No guidance on when to use this versus alternatives such as get_crawler_overview or submit_crawler_to_search, and no prerequisites or exclusions are stated. The pairing with submit_crawler_to_search is inferable only from the name, not from the description text.

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