Get Workspace Sso

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds no behavioral context beyond that, and its mention of a value being 'saved' is actually a mutation concern that belongs to setWorkspaceSso, which muddies rather than clarifies the read-only nature. It does not contradict the annotations outright, but it does not reinforce them either.

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?

It is a single sentence, which is appropriately sized, but it is not front-loaded with the tool's purpose and spends its only clause on fields the schema does not contain. Conciseness without relevance is not an asset here.

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 one-parameter read tool this should be easy to complete, yet the description omits what is returned (is `redirectUri`/`txtValue` part of the response?), the SSO state that might come back, and any distinction from `setWorkspaceSso`. There is no output schema to fall back on, so the description's silence on return shape is a real gap.

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 0% and the single parameter `workspaceSlug` is never mentioned in the description. Worse, the description explains `redirectUri` and `txtValue`, which are not parameters of this tool at all, so an agent reading it would be actively misled about what inputs exist. This is a hard miss on the one dimension where the description was needed most.

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 never states that this tool retrieves the workspace's SSO configuration; it only explains what `redirectUri` and `txtValue` mean. Since neither field exists in the input schema, an agent cannot even tell whether these are return values being previewed or something else. The name `getWorkspaceSso` does the actual work of conveying purpose.

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?

There is no explicit statement of when to call this versus `setWorkspaceSso` or `deleteWorkspaceSso`, both of which are the natural siblings. The phrase 'before it can be saved' vaguely gestures at a setup flow but never says 'call this to inspect SSO config before saving'. Fronting the ambiguity is left to the agent.

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