adtDiscovery

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Performs ADT discovery' gives no insight into whether this is a read or write operation, what permissions are required, if it has side effects, rate limits, or what the output looks like. The description is too vague to inform the agent about the tool's behavior.

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 concise with just three words, which avoids waste. However, it's under-specified rather than efficiently informative—it sacrifices clarity for brevity. While front-loaded, it fails to provide essential context, making it less helpful than a slightly longer but clearer description would be.

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 implied by the tool name 'adtDiscovery' among many sibling tools, the description is incomplete. No annotations or output schema exist to supplement it, and the description lacks details on purpose, usage, or behavior. It doesn't provide enough information for an agent to understand when or how to invoke this tool effectively.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter details, and it doesn't contradict the schema. A baseline of 4 is appropriate since there are no parameters to explain, and the description doesn't introduce confusion.

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 'Performs ADT discovery' is a tautology that restates the tool name 'adtDiscovery' without adding meaningful specificity. It doesn't explain what ADT discovery entails, what resources it operates on, or what the expected outcome is. While it includes the verb 'performs,' it lacks the clarity needed to distinguish this tool from its many siblings.

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?

The description provides no guidance on when to use this tool versus alternatives. With 100+ sibling tools including 'adtCoreDiscovery,' there is no indication of how this tool differs or when it should be selected. The description fails to mention any prerequisites, context, or exclusions for usage.

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