Get org domain sso verified

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, covering the safety profile. The description adds nothing further – no indication of what a verified/unverified response looks like, what happens if no domain claim exists, or any auth/permission expectations.

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?

A single tight sentence with no waste and the operation front-loaded. Its brevity is appropriate for the format, though it errs toward under-specification rather than over-verbosity.

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?

With no output schema, undocumented wrapper parameters, and only a read-only annotation set, the description is too thin to tell an agent how to form a correct call or interpret the result. It should at minimum identify the org parameter and the boolean/verified outcome.

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?

There are 3 parameters (form, params, json_body) with 0% schema description coverage, so the schema provides no semantics. The description only implies an org identifier is needed via 'an org's' but never explains which parameter carries it or its format, so it does not compensate for the coverage gap.

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 ('Check whether') and resource ('an org's SSO domain claim is verified'), so the operation is identifiable. It does not name the org identifier or differentiate from related sibling tools such as vaultwarden_get_settings_domains, leaving sibling routing to inference.

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 no explicit when-to-use context, prerequisites, or alternatives. The use case is only implied by the word 'Check', and there is no guidance on when this should be called versus fetching general org settings/domains.

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