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. However, it offers no information about what the tool does behaviorally—whether it's a read or write operation, what permissions are required, if it has side effects, rate limits, or what the output might look like. The phrase 'performs ADT discovery' is too vague to infer any behavioral traits.

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 a single sentence ('Performs ADT discovery.'). It is front-loaded and wastes no words, making it efficient to parse. However, this conciseness comes at the cost of clarity and completeness, but as per the scoring criteria, it earns full points for being appropriately sized with zero redundant content.

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, no output schema, and a vague description, the tool definition is highly incomplete. The description fails to explain what ADT discovery involves, what the tool returns, or any behavioral context. For a tool with no parameters, the description should at least clarify the purpose and output, but it does not, leaving significant gaps for an AI agent to understand its use.

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, and the schema description coverage is 100%, meaning there are no parameters to document. In such cases, the baseline score is 4, as there is no need for the description to compensate for missing parameter information. The description doesn't add parameter details, but none are required.

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 context. It doesn't specify what ADT discovery entails, what resources are involved, or what the outcome is. While it mentions the action ('performs'), it lacks specificity about what is being discovered or how this differs from sibling tools like 'adtCoreDiscovery'.

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. It doesn't mention any prerequisites, contexts, or exclusions, nor does it differentiate it from similar tools in the sibling list (e.g., 'adtCoreDiscovery'). Without such information, an AI agent cannot determine appropriate usage scenarios.

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