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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so 'Rein lesend' is redundant. The description still adds value by summarizing the returned content (fields, grouping, visibility) and by noting the identical-response relationship to ontouser_interface_show.

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 operative content is front-loaded and compact: read scope, safety, usage condition, alternative, and sibling equivalence. The trailing '| EN: onto, interface, show' keyword tag is mild filler but does not obscure the main guidance.

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?

With no output schema, the description supplies enough return-content context (fields, grouping, visibility) for the agent to know what a successful read provides. Annotations cover the safety profile, so the remaining gaps are minor.

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% for the single required 'name' parameter, and the schema already labels it 'Interface-Name'. The description reinforces that the name is the lookup key but adds no syntax, format, or qualification details beyond the schema.

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 states a specific verb and resource ('Ein einzelnes Interface vollstaendig lesen') and enumerates what is included: fields, grouping, visibility. It distinguishes itself from onto_interface_index and notes the identical-response sibling ontouser_interface_show, so the agent can select it confidently.

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?

Explicit routing is provided: use it when the name is known, and use onto_interface_index when it is not. It also clarifies that ontouser_interface_show returns the identical response, which prevents unnecessary tool shopping.

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