provider_get_org_ldap_settings

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, and the annotation title already contains the REST endpoint. The description contributes no additional behavioral context (no auth requirements, no indication of what is returned, no pagination or sensitivity notes). It does not contradict the annotations.

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 same sentence is stated twice verbatim, and the third line repeats the endpoint path already present in the annotation title. Only one of the three lines carries information, so the structure is padded rather than front-loaded.

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?

A parameterless, read-only GET is relatively simple, and the annotations cover the safety profile. But with no output schema, the description could have named what the settings object contains; 'all the LDAP settings' is the bare minimum an agent needs to act.

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 takes zero parameters and the input schema is an empty object, so there is nothing for the description to explain. Baseline 4 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 names a specific verb and resource ('Get all the organization LDAP settings'), which is enough to tell it apart from provider_update_org_ldap_settings or provider_search_ldap_users. However, it adds nothing beyond a restatement of the tool name, and offers no explicit differentiation from the many sibling 'get' tools (e.g., provider_get_org_settings).

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 guidance on when to call this versus related siblings such as provider_get_org_settings, provider_test_ldap, provider_search_ldap_users, or provider_update_org_ldap_settings. The agent must infer the scope from the resource name alone.

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