sap_read_dynpros

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It clearly indicates a read-only retrieval operation and states the output includes field lists, but it does not describe the response format, potential size, or any edge cases. For a simple read tool this is minimally adequate, but it lacks richer 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 is a single sentence with the action and primary object front-loaded, and it contains no filler or redundant details. It earns its place as an efficient summary for a simple tool.

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?

The tool has no output schema and no annotations, so the description must carry more weight. It gives a basic summary of what is retrieved but omits usage context, distinction from sibling read tools, and any indication of the returned structure beyond 'field lists'. It is usable but thin.

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 description coverage is 100%, so the schema already documents object_name and object_type. The description adds no parameter-level detail beyond what the schema provides; it only loosely says 'program' even though object_type allows PROG, CLAS, and FUGR, which the schema clarifies.

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 uses a specific verb ('Retrieves') and names a distinct resource ('screen definitions for a program including field lists'), so an agent can tell it returns dynpro screen metadata rather than code or table data. It does not explicitly contrast it with sibling tools like sap_get_field_metadata, but the resource is clear enough.

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 intended use is implied by the description—use it to get screen definitions—but there is no explicit guidance about when to prefer it over alternatives or when not to use it. No exclusions, prerequisites, or sibling comparisons are provided.

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