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

With no annotations, the description carries the full burden of disclosing side effects, read-only vs. write behavior, rate limits, or output format. The phrase 'Execute' implies running something, but nothing is disclosed about what happens during execution, whether it mutates state, or what the response looks like. This is a severe transparency gap.

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 concise writing. The single sentence adds no value beyond the tool name and fails to earn its place. It is comparable to the 'Process' example, which scored 2 for being too vague.

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?

Given the tool's high complexity (nested objects, two required parameters, no output schema) and zero annotation coverage, the description is completely inadequate. It provides no information about expected inputs, outputs, or behavioral constraints, leaving the agent to infer everything from the schema and sibling context, which is insufficient.

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 input schema is complex with nested objects (target, analysis) and many properties, but the description offers zero explanation of any parameter. It doesn't clarify what 'target', 'analysis', 'metrics', or 'matrix' mean or how they should be used. With 0% schema coverage, the description fails to compensate, leaving parameter semantics entirely dependent on the schema alone.

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 'Execute GEO analysis query.' uses a vague verb 'execute' and an ambiguous resource 'GEO analysis query'. It does not explain what the analysis entails, what kind of results are produced, or how it differs from sibling tools like get_keyword_volume or get_topics. The description essentially restates the tool name without adding meaningful specificity.

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 does not mention use cases, prerequisites, or scenarios where this tool is preferred. Sibling tools have varied purposes, but no comparative context is provided.

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