System profile and maintenance

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

Annotations already declare readOnlyHint, idempotentHint, closed-world, and non-destructive, so the safety profile is fully covered structurally. The description adds that it reveals enabled object types and safety settings, which is useful context, but says nothing about output format, cost, or what a failure response looks like. Adequate but not rich.

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?

Two sentences, zero filler. The content payload is front-loaded and the usage restriction follows immediately.

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?

For a small read-only diagnostic tool with a one-value parameter and full annotation coverage, the description covers what it returns and when to reach for it. No output schema exists, so the enumerated return fields do the necessary work; only failure-mode details are missing.

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?

There is one parameter, an 'action' enum with a single allowed value 'profile' and a default, so calling it is self-evident from the schema. Schema description coverage is 0% and the description never mentions the action parameter, but a single-value enum needs little explanation.

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?

States a specific resource and enumerates exactly what it returns: release, platform (BW/4HANA or classic), enabled object types, and active safety settings. An agent can tell this apart from siblings like bw_describe or bw_read, which operate on individual objects rather than system-wide configuration.

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?

Explicitly gives both a when and a when-not: call it only when a call fails for a system reason, not as a first step. The only gap is that it does not name a concrete sibling alternative for the first-step case, but the exclusion is unambiguous.

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