add_observer_to_document

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

Annotations already indicate this is a mutation (readOnlyHint=false) and not idempotent or destructive. The description adds the important timing constraint (before activation) and prerequisite steps, but does not disclose whether duplicates are allowed or what happens if called after activation. No contradiction with annotations.

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 three sentences, front-loaded with the action and definition, and every sentence provides useful context. No redundancy or wasted words.

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 the purpose, prerequisites, and timing, and an output schema exists for return values. It does not mention error conditions (e.g., after activation), but for a moderate-complexity add-operation this is reasonably complete.

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 coverage is 40%, and the description adds provenance for the ID parameters (create_signature_request → signatureRequestId, add_document_to_signature_request → documentId). However, name, email, and surnames are not explained beyond their schema types, leaving some gaps for a low-coverage situation.

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 verb 'Adds' and the resource 'observer to a signature request's document,' and it defines the observer's role as read-only without signing. This distinguishes it from sibling tools like add_signatory_to_document and add_validator_to_signatory.

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?

It explicitly says to add observers BEFORE activate_signature_request and supplies the required prerequisite flow (create_signature_request → signatureRequestId, add_document_to_signature_request → documentId). It does not explicitly name alternatives, but the 'without signing' clause differentiates from signatory-related tools.

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