adtCoreDiscovery

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. It states 'Performs ADT core discovery' but does not clarify whether this is a read-only operation, if it has side effects, what permissions are required, or how results are returned. For a tool with zero annotation coverage, this leaves critical behavioral traits unspecified.

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, efficient sentence with no wasted words. It is appropriately sized for a tool with no parameters and gets straight to the point, though the content itself is lacking in detail. The structure is front-loaded and concise.

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 and output schema, the description is incomplete. It does not explain what 'ADT core discovery' entails, what the tool returns, or any behavioral context. For a tool with no structured metadata, the description fails to provide sufficient information for an agent to understand its function and use it correctly.

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 input schema fully documents the absence of parameters. The description does not need to add parameter semantics, and it appropriately avoids discussing inputs. A baseline of 4 is warranted since no parameters exist to explain.

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 core discovery' is a tautology that essentially restates the tool name 'adtCoreDiscovery' without providing meaningful context about what 'ADT core discovery' actually does. It lacks a specific verb and resource, making it unclear whether this discovers system components, configurations, or something else. While it distinguishes from siblings by mentioning 'core' (vs. 'adtDiscovery'), the purpose remains vague.

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 like 'adtDiscovery' or other sibling tools. There is no mention of specific contexts, prerequisites, or exclusions. The agent must infer usage based on the tool name alone, which is insufficient for informed decision-making.

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