identity_overview

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

Annotations are absent, so the description must communicate side effects and behavior. The '[READ]' marker signals a non-mutating operation, and 'one-shot summary' suggests a bounded/fast response. However, it doesn't mention auth requirements, rate limits, output format, or what happens with the default target, leaving some burden unmet.

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 compact sentences plus an Args line; every sentence adds information. The 'Lead with this' instruction earns its place.

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?

Given a single optional param and no output schema, the description adequately covers the tool's role and return contents. It could be slightly richer (e.g., mention whether failed-login feed size is a count or a list), but for the intended overview purpose it is sufficient.

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 provides no description (0% coverage), only an optional 'target' with default null. The description fully clarifies that it is an IdP target name from config and that omitting it selects the default, which is all the agent needs for this single parameter.

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?

Description opens with '[READ]' and explicitly states the tool produces a one-shot summary with a specific inventory (platform/realm, counts, failed-login feed size). It also instructs 'Lead with this,' making clear this is the entry-point overview tool and distinguishing it from the detailed sibling tools.

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 says 'Lead with this,' which tells the agent to use it as the initial overview before querying details. It does not explicitly name alternatives or exclusion criteria, but the directive is clear enough.

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