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

With no annotations and no behavioral description, the agent has no information about side effects, required permissions, rate limits, or what happens when the tool is invoked. The description 'V1 Maps Jobs' discloses nothing beyond the tool's existence.

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?

The description is extremely short, but this is under-specification rather than conciseness. It contains no useful information and does not earn its place as a tool description.

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 tool with one required parameter, no output schema, no annotations, and three sibling tools, the description is completely inadequate. The agent lacks all context needed to select or invoke this tool correctly.

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?

The schema has one required parameter 'extra' with 0% description coverage, and the description does not explain what 'extra' means, its format, or its purpose. The agent cannot determine what value to provide.

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 'V1 Maps Jobs' is essentially a tautology that restates the tool name without any verb or resource. It does not state what the tool does, what a 'job' is, or how it differs from sibling tools like maps_results, maps_search, or maps_status.

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 guidance on when to use this tool versus alternatives. The description provides no context, conditions, or exclusions, leaving the agent to guess whether this is for creating, listing, or managing jobs.

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