query_response_artifact

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

With no annotations, the description must disclose behavior. It implies a read operation ('Query') but does not state explicitly that it is non-destructive, nor does it mention authentication, rate limits, or side effects. The vague 'bounded, strict camelCase controls' hints at input validation but nothing actionable.

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 a single concise sentence that is not bloated, but the phrase 'bounded, strict camelCase controls' is cryptic and wastes space on vague terms instead of useful detail. It is not front-loaded with the most 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 complexity (10 parameters, no output schema, no annotations), the description is severely inadequate. An agent cannot determine how to construct a valid request, interpret the response, or understand pagination, filtering, or field selection. The description is nearly useless for this 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?

Schema coverage is 0%, and the description adds no meaning to any of the 10 parameters. It does not explain cursor, fields, filters, describe, pageSize, objectMode, textSearch, responsePath, or even the required environment and artifactId. The phrase 'strict camelCase controls' is too abstract to help an agent understand parameter formats.

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 states a clear verb and resource: 'Query a stored provider response.' It does not explicitly distinguish from siblings, but the resource is distinct enough. The phrase 'bounded, strict camelCase controls' hints at parameter constraints but is vague, missing specifics like filtering or pagination.

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 alternatives like proxy_request or download_provider_file. There is no mention of prerequisites, context, or scenarios where this tool is preferred.

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