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

With no annotations, the description carries the burden of behavioral disclosure)Skip and it does add meaningful behavior: sharing a single in-flight job limit with the web app and returning 409 if another job is running. It does not mention the success response shape or asynchronous behavior, but the stated concurrency failure mode is valuable.

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 with no filler: the first states the operation and constraint, the second gives the critical concurrency error. Every word earns its place and the key information is front-loaded.

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 one-parameter create tool, the description covers the essential input and a key error condition. However, because there is no output schema, it does not explain what a successful call returns or how to obtain the job's results, leaving that to inference from sibling tools.

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 100%, so the schema already documents the keyword parameter with an example. The description's 'exactly one keyword' reinforces the schema but does not add new meaning beyond it.

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 clearly states that this creates a Maps search job for a single keyword, using a specific verb and resource. It distinguishes from sibling photo/review job creators by saying 'search job,' though it does not explicitly name the alternative tools.

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 description implies usage for one-keyword Maps searches via 'exactly one keyword,' and the 409 conflict note warns against concurrent calls. However, it does not explicitly say when to prefer this over gmaps_create_photos_job or gmaps_create_reviews_job, so routing relies on inference from sibling names.

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