discover_documents

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

No annotations are provided, so the description must fully convey behavioral traits. It does not indicate whether the tool is read-only, destructive, or what side effects occur (e.g., creating resources, modifying state). The phrase 'launch discovery' implies an asynchronous operation, but no details are given.

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 extremely short (one sentence), but it is under-specified rather than concise. It fails to convey necessary information about the tool's purpose, parameters, and behavior, making it insufficient for reliable selection and invocation.

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 lack of annotations, output schema, and parameter descriptions, the description is woefully incomplete. It does not address the complexity of the tool (single generic parameter, no return value info), leaving critical gaps for the agent.

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 'kwargs' is generic and lacks description in both the schema and the tool description. With 0% schema description coverage, the description adds no meaning to the parameter, leaving the agent completely uninformed about required or optional input structure.

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 the action ('launch discovery') and the resource ('existing KFabric query'), but 'discovery' is vague and not elaborated, leaving ambiguity about what the tool accomplishes. It distinguishes from siblings like 'create_query' by specifying an existing query, but lacks clarity on the meaning of 'discovery'.

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 on when to use this tool versus alternatives like 'analyze_document' or 'create_query'. The description does not mention prerequisites, contexts, or exclusions, leaving the agent to infer usage from the name alone.

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