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

With no annotations, the description does carry the most important behavioral fact: the call is a no-op because there is no session state, so invoking it has no side effect. It does not say what the call returns (empty result? error?), nor what the single `_org` parameter does.

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 short sentences, front-loaded with the key fact that this is a no-op. The ADR citation is internal noise that does not help an agent decide or call correctly.

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-optional-parameter tool with no annotations and no output schema, the description covers the no-op nature but leaves the parameter undocumented, the return behavior unknown, and the distinction from the use_group/clear_org siblings unstated.

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 0% and the description never mentions the only parameter, `_org`. Worse, it discusses a `_group=` token that does not exist in this tool's schema, which can send the agent looking for a parameter it cannot pass here.

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?

"No-op hint" tells the agent the call does nothing, which is a behavioral statement rather than a purpose, and the description never says what clearing a group would conceptually do or how oto_clear_group relates to oto_use_group / oto_clear_org. The reference to "ADR 0038" is internal documentation jargon the agent cannot resolve, so the stated rationale is opaque.

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?

It implicitly steers the agent away from this tool by explaining that group scoping is expressed per-call via a `_group=` token and that the durable default lives in the dashboard. That is real routing guidance, but it never names the concrete alternative tools (oto_use_group, oto_clear_org) nor states explicitly "do not call this".

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