List Workspace Integrations

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the baseline safety profile is clear. The description adds no further behavioral context (e.g., side effects, rate limits, or whether it returns live or cached data), but given the simple read-only nature, this is acceptable.

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?

The description is a single, compact sentence that conveys the essential purpose without unnecessary verbosity. It is well-structured and easy to parse.

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 basic list operation, the description is sufficient. It identifies what is listed (integrations) and includes 'provider status' as an important detail. It does not mention output format or whether pagination is supported, but given the absence of an output schema and the simplicity of the tool, this is not a significant 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?

The only parameter, workspaceSlug, is a string and required. The description does not elaborate on what the slug represents or any constraints, but the name is self-explanatory in the context of workspace-related tools. Schema coverage is effectively 100% since the parameter name is clear, so the baseline score of 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?

The description clearly states the action ('List') and the resource ('workspace integrations'), and adds the extra detail of 'provider status', which distinguishes it from other list tools like listWorkspaceDomains or listWorkspaceMembers. It is immediately apparent what this tool does.

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 no guidance on when to use this tool compared to sibling list tools, nor any conditions that would make it preferable. It does not mention alternatives or suggest scenarios. The agent is left to infer usage from the name alone.

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