Deluge Examples

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

No annotations are provided, so the description carries full behavioral burden. It mentions ranking, confidence, and safety filters, but never explains what 'safety filters' are, whether the operation is read-only, or what side effects or access requirements exist.

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 single sentence is tight and front-loads the main action, with no filler words. However, the brevity crosses into under-specification given the tool has 10 undocumented parameters and no additional context.

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?

With 10 optional parameters, 0% schema coverage, no annotations, and no output schema, the description is far from complete. It does not explain ranking semantics, memory/result limits, or how safety filters and parameters interact.

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 has 10 parameters with 0% description coverage in the schema. The tool description only echoes 'topic/query' and leaves unexplained parameters such as canonical_key, include_match_debug, require_source_allowlist, and service_scope, making it impossible for an agent to understand their semantics.

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 clearly states the action ('Return') and the resource ('Deluge examples'), with useful modifiers like 'ranked', 'high-confidence', and 'by topic/query'. It does not explicitly differentiate from siblings such as deluge_explain or zoho_crm_js_examples, but the core purpose is unambiguous.

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 deluge_validate, deluge_fix, deluge_explain, or zoho_crm_js_examples. The only contextual cue is 'by topic/query', which implies search usage but does not state when this is preferred or what alternatives exist.

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