Update domain

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

No annotations are provided, so the description carries the full burden. It discloses partial-update semantics (only passed fields change) and the iOS AASA caching delay (up to 24h), which are non-obvious and valuable. However, it does not mention authentication, error handling, or response 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?

Two sentences, front-loaded with verb+object, and no fluff. The caching caveat is important and concisely stated.

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?

Given nested objects and no output schema, the description covers key semantics (partial update, platform scope, caching delay) but omits response format and error conditions. Still, it is reasonably complete for the tool's complexity.

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 low (33%), but the description adds meaning by explaining that ios and android represent platform configuration and that only passed fields change. It does not describe id or sub-property details, leaving much to the schema.

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?

States 'Update a domain's iOS/Android configuration' with a specific verb and resource, clearly distinguishing from sibling tools like get_domain, create_domain, and verify_domain. The partial-update note further clarifies the tool's scope.

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?

Implies usage for updating existing domain configurations rather than creation or retrieval, providing clear context via the 'update' verb and partial-update behavior. Does not explicitly name alternatives like create_domain, but the context is sufficient.

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