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

Annotations already disclose a lot: readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the agent knows this is a non-destructive but non-idempotent external write. The description adds only the brand-scoping notion and the comma-separated URL format; it says nothing about auth requirements, rate limits, or what a submission actually does downstream.

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?

Front-loaded one-line purpose followed by a compact args list; nothing is padded or redundant. The args block restates requiredness already enforced by the schema, which is minor waste but not harmful.

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 open-world, non-idempotent submission tool with no output schema, the description covers the required inputs and the safety profile is carried by annotations. What's missing is workflow context — whether a status check is needed afterwards or what a successful submission returns — leaving the agent with a minimally viable picture.

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 coverage is only 33% (only user_intent is documented), so the description must compensate — and it does, explaining that brand_id is the brand to update (required) and urls are comma-separated absolute URLs, which is meaningful detail beyond a bare string type. It omits the user_intent param, but that one is already covered by the 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?

States a concrete verb+resource: submitting crawler URLs to AI search. An agent can identify the action immediately. It does not, however, differentiate itself from nearby siblings like get_crawler_submit_status or send_crawler_verification_ping, 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?

There is no when-to-use guidance, no prerequisites (e.g. does the crawler need access configured first?), and no mention of the submit-status sibling to check results. The description only says what the tool does, not when to reach for it.

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