add_trusted_domain

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

The description discloses a non-obvious behavior: 'First checks current trusted domains to assign the next available index.' This goes beyond a simple statement of purpose. However, it does not mention potential error conditions or side effects like config reload, but with no annotations, this is a reasonable burden.

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 concise, containing only three sentences. It front-loads the purpose, then adds the index-assignment behavior, and ends with a dedicated Args section. There is no filler or redundancy.

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?

For a single-parameter tool, the description covers purpose, behavior, and parameter semantics. The presence of an output schema makes it unnecessary to describe return values. It could be improved by mentioning when to use this versus get_trusted_domains, but that is not critical.

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 input schema only provides a string parameter with no description. The description adds meaning by specifying 'Domain name or IP address' and giving examples ('cloud.example.com' or '192.168.1.100'), which clarifies the accepted format.

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 'Adds a new trusted domain to Nextcloud config' with a specific verb and resource. It distinguishes from sibling tools like get_trusted_domains by using 'add' rather than 'get'.

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 intended use is clear from the description, but it does not explicitly mention alternatives or exclusions. It does not say when to prefer this over get_trusted_domains, though the verb 'add' makes the primary use obvious.

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