DataPreview

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

No annotations are provided, so the description must carry the burden of behavioral info. It does not disclose that the operation is read-only, what happens if the entity does not exist, the output format, or any rate limits. The description adds minimal value beyond the name.

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 only one sentence. However, it lacks essential information; brevity at the expense of completeness reduces effectiveness. Still, it is well-structured with no fluff.

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 (2 params, no output schema, no annotations), the description is incomplete. It does not mention the output format (e.g., JSON array), pagination, or any limitations. A preview tool should describe what the agent gets back.

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?

Schema coverage is 100%, so the input schema already documents both parameters. The description does not add meaning beyond the schema, such as explaining that rowNumber has a default or that ddicEntityName is the case-sensitive name. Baseline score.

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 'Preview', resource 'ABAP data', and target 'DDIC entity'. It distinguishes from sibling tools that focus on metadata (e.g., GetDDIC_Table, GetDDIC_Structure) by indicating this tool retrieves actual data rows.

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?

No usage guidelines are provided. The description does not tell when to use this tool over alternatives like GetDDIC_Table or GetDDIC_Structure, nor does it mention prerequisites or typical contexts.

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