Run a registered analytics operation (zonal_stats / time_series / change_detection).

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

Annotations declare readOnlyHint=true, so the agent already knows it is a read operation. The description adds no additional behavioral context such as rate limits, authentication requirements, or data returned. Since annotations carry the burden, a score of 3 is appropriate.

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 very short (one sentence) but lacks substance. It is not concise in a helpful way; it is simply minimal. While it is front-loaded, it omits critical information.

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 has 3 parameters, nested objects, and an output schema, the description is severely incomplete. It does not explain what operations are registered, how to pass params, or what the output contains. The agent would struggle to use this tool correctly without additional context.

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 description adds almost no value beyond the input schema. The schema provides descriptions for 'operation' and 'params'. The description only repeats 'Run a registered analytics operation' and lists examples, which does not clarify the meaning of the parameters further. Schema coverage is 67%, but the description does not compensate for the undocumented 'x-api-key' parameter.

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?

Tautological: description restates name/title.

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 on when to use this tool versus alternatives. For instance, it does not mention that operations must be already registered or that analytics.operations.list can be used to discover available operations.

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