syncthing_ignore_defaults

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. The description adds nothing beyond that: no indication of what data is returned, whether it reads Syncthing's built-in ignore defaults, or how instances/fields affect behavior.

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?

It is short, but this is under-specification rather than conciseness. The single fragment carries no usable information.

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 tool with two parameters at 0% schema coverage, no output schema, and only a two-word description leaves the agent unable to determine the operation's semantics or result. It is not complete enough to call correctly.

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% with two undocumented parameters (fields, instance), and the description mentions neither. It provides no meaning for what 'fields' selects or what 'instance' scopes.

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?

"Ignore defaults." is a fragment that essentially restates the tool name without a verb or object. It never states whether it returns default ignore patterns, resets them, or toggles ignoring of defaults, and it does not differentiate from siblings like syncthing_ignores or syncthing_folder_defaults.

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 when-to-use guidance, no conditions, and no mention of any alternative tool. An agent has no basis for choosing this over syncthing_ignores.

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