syncthing_ldap_config

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is known without the description. However, the description adds nothing beyond that: it doesn't say whether this returns the configured LDAP settings, whether it is per-instance, or whether credentials are involved, despite openWorldHint suggesting external interaction.

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 only two words, but this is under-specification rather than conciseness. It is front-loaded only in the sense that there is nothing else to say.

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 two undocumented parameters, no output schema, and no useful description, the definition is inadequate. For a tool sitting among 39 Syncthing siblings, an agent has no basis for selecting or correctly invoking it.

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 neither 'fields' nor 'instance' is documented in the schema. The description contributes zero meaning for either parameter, leaving the agent unable to know what 'fields' selects or what an 'instance' identifier refers to.

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 'Ldap config.' merely restates the tool name and does not state a verb or what operation is performed. It is a near-tautology: the agent learns only that LDAP configuration is involved, not whether it reads, lists, or sets it.

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?

No guidance whatsoever on when to use this tool versus the many siblings such as syncthing_config, syncthing_gui_config, or syncthing_instances. No preconditions, exclusions, or alternatives are mentioned.

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