get_envelope

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

No annotations provided, so description must fully address behavioral traits. It implies a read-only operation but does not explicitly state idempotency, safety, or request limits. The listed statuses hint at output but lack comprehensive disclosure.

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?

Single front-loaded sentence with a useful list of statuses. Efficient and targeted, though the status list could be structured as part of the output description. No extraneous content.

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 the simplicity of the tool (1 required param, no output schema), the description covers the main purpose and return content. However, it omits details like error scenarios, response format, or any behavioral notes, leaving some gaps.

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 0%; description does not elaborate on envelopeId beyond what the schema provides (format: uuid). The description focuses on return values rather than parameter meaning, adding no extra semantic value.

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?

Description clearly states 'Get envelope status including per-recipient progress', specifying the verb and resource. It distinguishes from sibling tools like list_envelopes (list) and create_envelope (create), but does not explicitly contrast them.

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?

No guidance on when to use this tool versus alternatives. No prerequisite conditions, exclusions, or context about when to prefer get_envelope over other tools.

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