Fetches the tenant-wide content security settings for Security Director Cloud, providing the current security configuration to assess and enforce content security policies.
Get the tenant-wide content security settings singleton.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavior. It only states 'Get', indicating a read operation, but fails to mention authorization requirements, what happens if the singleton is not configured, or any side effects. For a simple getter, this is minimal disclosure.
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 sentence that is front-loaded and contains no extraneous information. Every word serves a purpose, making it highly concise and efficient.
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?
Given the simplicity of the tool (no parameters, no output schema), the description is adequate but lacks details about the return value format or behavior when settings are absent. It meets the minimum viability but could be more complete.
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 tool has no parameters, and the schema coverage is 100% (vacuous). The description adds no parameter info, but none is needed. According to calibration, a baseline of 4 is appropriate for zero-parameter tools when the purpose is clear.
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 verb 'Get' and the specific resource 'tenant-wide content security settings singleton'. It effectively distinguishes this tool from siblings like 'sdcloud_get_content_security_profile' and 'sdcloud_set_content_security_settings' by specifying 'settings' vs 'profile' and indicating it's a singleton.
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 implies basic usage (retrieve settings) but provides no explicit guidance on when to use this tool versus alternatives, such as when to use profile-specific getters or the set tool. No exclusions or context are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.