Export SAP ADT Discovery

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

Annotations provide some safety context (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds that the output is 'temporary', which is useful. However, it does not disclose side effects (e.g., whether data is stored), permissions needed, or what 'full ADT discovery data' entails. Overall, adds marginal value beyond annotations.

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 sentence with no extraneous content. However, it sacrifices necessary detail for brevity, leaving key information unstated. It is concise but not sufficiently informative.

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 tool's simplicity (one parameter, output schema exists), the description should clarify the scope of 'ADT discovery data', the purpose of the export, and any side effects. It fails to provide enough context for an agent to understand when and how to use the 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 input schema has one required parameter 'systemId' with no description (schema coverage 0%). The description does not explain the parameter's meaning, format, or constraints beyond the schema's minLength. The agent must infer from the parameter name alone.

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 clearly states the verb 'export' and the resource 'full ADT discovery data' with a specific outcome 'to a temporary JSON artifact'. It distinguishes the tool's purpose from sibling tools, as no other sibling has a similar description. However, it does not explicitly differentiate itself from siblings or note uniqueness.

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. No prerequisites, context, or exclusions are mentioned. The description lacks instructions for appropriate usage scenarios.

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