Set Login URIs

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

The description correctly indicates mutation (set/update) consistent with non-readOnly annotations. It adds details on mode behavior and match values but does not cover side effects, permissions, or error cases.

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 two sentences, front-loaded with the core action, and every sentence adds necessary detail without 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?

The description covers mode and uris but omits explanation of the id parameter (required, described in schema) and reveal parameter (boolean), leaving some gaps for a tool with 4 parameters and no output schema.

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?

With 100% schema coverage, the description adds value by clarifying mode (replace vs merge) and explaining match value options (domain, host, startsWith, etc.), which goes beyond the schema's enum definitions.

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 the tool sets or updates URI lists on a login item, specifying two modes (replace and merge) and listing match values, distinguishing it from other keychain tools that handle different item types.

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 explains the two modes and match semantics but does not explicitly guide when to use this tool versus alternatives like editing other fields or using different keychain tools.

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