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

With no annotations provided, the description must disclose all behavioral traits. It does not mention whether the tool is read-only, what it returns, if there are side effects, or any constraints. The single phrase conveys nothing about behavior.

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, which might seem concise, but it is under-specified rather than efficiently informative. It lacks essential content that would make every word earn its place.

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 no annotations, no output schema, and a single optional parameter, the description is wholly inadequate. It does not clarify the purpose, return value, or relationship to sibling tools, leaving the agent without enough information to invoke it 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?

Schema description coverage is 0%, and the description does not explain the 'job_id' parameter at all. The schema itself only provides the type and default, so the agent has no understanding of what the parameter means or how to use 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 'V1 Maps Status' provides only a hint that this tool relates to status information for maps, but does not state a clear verb or resource. It is not a pure tautology, but it fails to distinguish from siblings like maps_jobs or maps_results. An agent cannot tell what this tool actually does beyond a vague 'status' notion.

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 is given on when to use this tool versus the sibling tools. There is no mention of scenarios, alternatives, or exclusions. The description offers no context for selection.

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