Who am I on OCI

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description goes beyond them by disclosing what is actually exposed (tenancy, user, region, auth method, which compartments may be mutated, capability flags) — security-relevant context about what the call reveals. Minor gap: no note on latency, caching, or whether identity can change mid-session.

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?

Three short sentences, each load-bearing: what it reports, exactly what comes back, and when to call it. Front-loaded with the verb and outcome; no filler or restatement of the title.

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 values need not be spelled out, yet the description still summarizes them usefully. Combined with annotations covering the read-only/idempotent profile and a zero-parameter schema, an agent has everything required to invoke this correctly as a session-opening call.

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 tool takes zero parameters, so per the rubric the baseline is 4. Nothing in the description is needed to clarify arguments, and nothing is misleading about input.

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?

Specific verb ('Report') plus a precisely scoped resource: the active OCI identity and the server's own permissions. It further enumerates the exact fields returned (tenancy, user, region, auth method), which no sibling tool (oci_list/oci_get/oci_search) does, so an agent can distinguish it immediately.

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?

Gives an explicit sequencing rule: 'Call this first in a session to learn what is reachable before acting.' That is clear, actionable when-to-use guidance. It does not explicitly name the sibling tools or state when not to use it, but the intent is unambiguous.

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