adtCoreDiscovery

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states 'Performs ADT core discovery' without mentioning side effects, return values, required preconditions like login, or any operational behavior. This is completely inadequate for a tool with no annotation support.

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 this is under-specification, not conciseness. It omits all meaningful information, so the brevity is not a virtue; it fails to earn its place by adding value.

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 there are no annotations, no output schema, and an empty parameter schema, the description is the sole source of context. It fails to explain what ADT core discovery does, what inputs or outputs are involved, or how it relates to the many sibling tools, making it severely incomplete.

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 is empty with 0 parameters, and the baseline for 0 params is 4. The description adds no parameter-specific information, but there are no parameters to document, so nothing is missing.

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 essentially a restatement of the tool name with a generic verb. It identifies a resource ('ADT core discovery') but does not define what that resource is or what 'discovery' accomplishes, nor does it distinguish this tool from the sibling 'adtDiscovery'.

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 alternatives such as adtDiscovery or adtCompatibiliyGraph. No context, prerequisites, or exclusions are provided; the description only states the action without any situational advice.

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