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

Annotations already establish readOnly/idempotent/non-destructive, so the bar is lower. The description still adds genuine behavioral context beyond structured fields: the auth requirement (owner/admin only) and the strong safety guarantee that secrets and API key values are never returned.

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?

Purpose is front-loaded in the opening clause and the content enumeration is dense but earns its place by previewing the return shape. The two trailing sentences (no secrets, owner/admin only) are quick and high-value, though the list runs long.

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, the description carries the burden of describing returns, and it does so by enumerating the settings returned. It covers access requirements and the secrets caveat, leaving only minor gaps such as error behavior or output formatting.

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?

Only one parameter exists with 100% schema description coverage, so the schema already documents org_id fully. The description adds no syntax or format detail beyond it; baseline 3 applies when the schema does the heavy lifting.

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 (Read) and resource (security settings of an organization) and enumerates the exact contents returned (2FA requirement, public links, retention, sharing limits, API keys, SCIM, audit log stream). This clearly distinguishes it from siblings like get_organization and get_org_audit_log.

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 usage (read security settings) and adds an access prerequisite ('Only an owner or an admin can see it'), but gives no explicit when-to-use/when-not guidance and does not name alternatives such as update_org_security or get_organization.

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