Create OIDC App

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

Annotations include openWorldHint, indicating the tool creates new resources. The description adds behavioral context about default values for unspecified fields, which is useful beyond the annotation but does not cover other traits like idempotency or error handling.

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?

Single sentence that is concise and front-loaded with the tool's purpose. Every part is informative, 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?

The description lacks explanation of return values or error cases, but the input schema is well-documented with examples. Given the tool's complexity (nested objects), the description could mention what the response looks like, but the schema compensates partially.

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?

All 5 parameters have schema descriptions (100% coverage). The description adds value by noting that only desired oauth2Client fields need to be supplied, with defaults applied for the rest. This goes beyond the schema's structural definitions.

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 clearly states 'Creates an OIDC application', which is a specific verb+resource. It distinguishes from sibling tools like deleteOidcApp and updateOidcApp. The additional guidance about defaults adds clarity.

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?

Description advises 'Only supply the oauth2Client fields you want to set; defaults are applied for the rest.' This gives usage context but does not explicitly contrast with alternative tools like updateOidcApp, nor does it state when not to use this tool.

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