Api ebios rm operating modes retrieve

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description contributes one genuinely useful behavioral fact beyond them: unauthorized related fields are masked, which matters for interpreting results. It stops short of describing what is masked or returned.

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?

One short sentence with no padding, so it is efficient, but the space saved is spent on ambiguity rather than a front-loaded statement of what is retrieved.

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 single-object retrieval with no output schema, the description should at least identify the returned entity and the id semantics. It covers only the masking caveat, leaving the caller to infer the rest from the tool name.

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?

The single required parameter 'id' has 0% schema description coverage and the description says nothing about it — no format, no indication of whether it is a UUID, numeric id, or ref. With low coverage the description needed to compensate and does not.

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 says only 'Return a single object' and never names the resource; the actual object (an EBIOS RM operating mode, fetched by id) is inferable only from the tool name. It adds the masking detail but leaves the core purpose unstated.

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 when-to-use guidance and no mention of alternatives, despite close siblings such as operating_modes_object_retrieve, operating_modes_list, and operating_modes_cascade_info_retrieve. An agent gets no help choosing between them.

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