execute_wcps_query

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

Describes return value structure and includes an important instruction to show the query and file path. With no annotations, this provides good transparency, though it does not mention side effects or permissions.

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?

Four sentences, front-loaded with purpose, followed by return details and a key instruction. No unnecessary text; every sentence adds value.

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?

Covers purpose, usage, return format, and an actionable instruction. Lacks parameter specifics, but the output schema exists to supplement. Nearly complete for a single-parameter execution tool.

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 only parameter, wcps_query, lacks any description in the schema (0% coverage). The description only states it is a WCPS query, adding minimal meaning beyond the obvious from the tool name. No format or constraint details are provided.

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?

Clearly states the verb 'Executes' and the resource 'WCPS query in rasdaman'. Specifies its use for spatio-temporal operations, distinguishing it from sibling tools like describe_coverage or list_coverages.

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?

Explicitly mentions use cases like subsetting, processing, aggregation, filtering. Lacks explicit when-not-to-use or alternatives, but the sibling context makes the differentiation clear.

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