provider_delete_oidc_relying_party

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the description must add context such as irreversibility, effect on tokens/sessions issued to that relying party, or required auth. Instead it restates "delete" twice and pastes the HTTP route, adding nothing beyond structured data.

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?

Short overall, but the first two lines are the same sentence repeated and the third is a raw endpoint that duplicates the annotation title. It is front-loaded and small, yet a third of the content is pure redundancy.

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 destructive, irreversible delete with no output schema, an agent needs to know consequences (e.g., clients using that relying party lose SSO) and the idempotency/error behavior. The annotations hint at the safety profile, but the description supplies none of the operational context a caller needs before executing.

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 description coverage is 100% and the single id parameter is already documented as the relying party's ID path parameter. The description adds no format, sourcing, or lookup guidance, so baseline 3 applies.

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?

States a specific verb and resource ("Deletes a specific OIDC relying party") and the REST endpoint, which makes it distinguishable from provider_get_oidc_relying_party, provider_update_oidc_relying_party, and provider_register_oidc_relying_party by verb alone. No explicit sibling comparison, but the name-plus-verb is unambiguous.

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?

No guidance on when to use this versus alternatives such as provider_query_oidc_relying_parties (to look up the id first) or provider_update_oidc_relying_party. Nothing about prerequisites, permissions, or the caution warranted before a destructive delete.

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