adtDiscovery

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

No annotations are provided, so the description must fully disclose behavioral traits. 'Performs ADT discovery' offers no information on what the tool does operationally—whether it's a read-only scan, a configuration change, or something else. It lacks details on permissions, side effects, rate limits, or output format, leaving the agent with no actionable behavioral context.

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 'Performs ADT discovery' is overly concise to the point of under-specification. While it uses only three words, it fails to convey essential information, making it inefficient rather than succinct. Every sentence should earn its place, but this one provides minimal value, indicating poor structure for tool selection.

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 sibling tools and the lack of annotations and output schema, the description is severely incomplete. It does not explain what ADT discovery entails, what results to expect, or how it differs from similar tools. For a tool in a rich ecosystem, this minimal description leaves critical gaps in understanding its role and behavior.

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, meaning the input schema fully documents the absence of parameters. The description does not add parameter semantics, but since no parameters exist, this is acceptable. A baseline of 4 is appropriate as the schema handles the parameter aspect completely.

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 essentially restates the tool name 'adtDiscovery' with minimal elaboration. While it indicates the tool relates to ADT (presumably ABAP Development Tools) discovery, it lacks specificity about what resources or operations are involved, making the purpose vague and indistinguishable 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 does not mention any context, prerequisites, or exclusions, and with sibling tools like 'adtCoreDiscovery' present, there is no differentiation to help an agent choose appropriately. This absence of usage instructions is misleading in a complex environment.

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