client_misconfig_audit

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly says '[READ]' indicating a non-mutating operation, and it proactively reveals a critical caveat: 'inputsTruncated' returns true when max_clients is hit, warning that a clean result over a clipped list is not evidence of a clean estate. This is valuable behavioral transparency beyond the basic read intent.

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?

The description is well-structured and front-loaded. It starts with a concise summary of the tool's purpose and risk categories, then clearly separates 'Args' and 'Returns' sections. Every sentence earns its place—even the caveat about inputsTruncated is essential context. It is compact but comprehensive, with no wasted words.

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 that there is no output schema and no annotations, the description provides a good amount of context: it explains the main output (per-client riskScore, evidence, actions) and the truncation behavior. However, it does not fully specify the return structure (e.g., exact fields of each client object, shape of the response). It is complete enough for an agent to understand what is returned, but could be more explicit about the full output schema.

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 schema has 0% description coverage for parameters, but the description fully compensates by explaining both parameters: 'max_clients: Clients to pull (default 200)' and 'target: IdP target name from config; omit for the default.' This adds meaningful semantics that the schema alone (types/defaults only) does not provide, such as the meaning of target and the truncation-related purpose of max_clients.

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 clearly identifies the tool as a read-only audit for OAuth/OIDC client misconfigurations, listing specific risk factors (wildcard redirect URIs, public clients with secrets, implicit flow, missing PKCE, password grant) and stating it produces per-client riskScore with evidence and actions. This is a specific verb+resource that distinguishes it from siblings like list_clients or client_detail.

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?

The description gives clear context: it is the tool to use for auditing ranked client risk, as evidenced by the enumerated misconfiguration categories and the audit-focused language. It does not explicitly exclude other tools or name alternatives, but its scope is unmistakable—there is no ambiguity about when to use it.

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