kwfinder_kd_requests

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

With no annotations, the description carries the full burden of behavioral disclosure. It states only that the tool retrieves history, implying a read operation, but provides no details on pagination, response format, rate limits, or required authentication. This is a significant gap for a tool with generic pass-through parameters.

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 sentence with no wasted words, making it highly concise. However, it is so terse that it misses opportunities to add valuable context, so it earns a 4 rather than a 5.

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?

The tool has generic pass-through parameters, no annotations, and no output schema. The description only names the purpose without explaining expected inputs, response characteristics, or integration with the Mangools API. An agent would struggle to correctly invoke this tool without additional information.

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?

Although the schema has 100% description coverage, the descriptions for 'body' and 'query' are generic boilerplate applicable to any endpoint, offering no tool-specific meaning. The description itself does not mention any parameter names or structures, leaving the agent without clues on what to pass for a KD history lookup.

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 uses the verb 'Get' and identifies the resource as 'KWFinder KD lookup history', which clearly states the core function. It also distinguishes itself from sibling tools like 'kwfinder_requests' by focusing specifically on KD history, though it does not elaborate on what constitutes 'history' in this context.

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 provided regarding when to use this tool versus alternatives such as 'kwfinder_requests' or 'kwfinder_limits'. The description simply states what it does without any context on appropriate use cases or exclusions.

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