Get OIDC App Schema

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

The description adds value beyond the annotations (readOnlyHint, openWorldHint) by explaining the output modes (summary vs. full details) and the recommended prior usage. There is no contradiction with annotations; the behavior is clearly a safe read operation that returns schema information.

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 sentences, front-loaded with the core purpose, followed by usage guidance. Every sentence adds essential information. No filler or repetition of schema details. Highly efficient.

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 read-only schema retrieval tool with fully described parameters and annotations, the description is complete. It covers the tool's purpose, modes, and usage context. No output schema exists, but the description explains what will be returned (a compact summary or full schema). The agent can correctly decide to invoke this tool.

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?

Input schema has 100% description coverage, so the baseline is 3. The description echoes the summary parameter behavior but adds no additional semantic meaning beyond what the schema already provides. It does not explain other parameters like sections or includeDefaults beyond their schema descriptions.

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 states the tool returns the schema for an OIDC application, distinguishes between compact summary and full details, and explicitly tells the agent to call it before createOidcApp or updateOidcApp. This differentiates it from sibling tools like createOidcApp that actually create the application.

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 provides explicit guidance: 'Call this before createOidcApp or updateOidcApp to understand available fields.' This tells the agent precisely when to use the tool and sets the context for subsequent mutations. It implicitly advises against using it for other purposes.

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