Get Object

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered structurally. The description adds one genuinely useful behavioral detail beyond that: secrets are redacted while other metadata is preserved. It says nothing about auth requirements, error behavior, or size/rate limits on large definitions.

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?

A single tightly written sentence with no filler, and the core operation is front-loaded. It is arguably too terse for a four-required-parameter tool, but nothing in it is wasted.

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?

An output schema exists, so return-value documentation is not needed, and annotations cover the safety profile. Still missing for a four-parameter lookup tool is any indication of which object_type values matter, what happens on a missing object, or how this fits alongside get_dependencies.

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 0% across four required parameters, so the description must carry the load and does not: it never explains environment, space, object_type, or technical_name. The enums and patterns in the schema partially self-document environment and object_type, but the description contributes no semantics at all.

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 names a specific verb ('Read') and resource ('the original SAP CSN/JSON definition'), so the agent knows it retrieves a single object's raw definition rather than a list. It does not explicitly contrast with siblings like list_objects or get_dependencies, but the get-vs-list distinction is inferable from the name and phrasing.

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 reach for this tool versus list_objects or get_dependencies, and no mention of preconditions such as needing a known technical_name or a valid environment/space combination. Usage must be entirely inferred from the tool name.

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