get_customer_context

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

Discloses the tool gathers org, tickets, and issues—a read-only operation. Without annotations, description carries burden; no side effects or limitations (e.g., data freshness, rate limits) are mentioned, but basic behavioral context is provided.

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, zero waste. First sentence states purpose, second gives usage guidance. Efficient and well-structured.

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 no output schema, the description adequately explains output: org, past tickets, prior issues. Could specify format or additional details, but sufficient for understanding the tool's value.

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 has 100% coverage with basic descriptions. The description adds value by differentiating the two parameters: organization for whole account, requesterEmail for single contact, and gives an example ('Anthology').

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 pulls together customer information including org, tickets, and issues. It distinguishes from sibling tools like search_similar_tickets by focusing on customer context rather than similarity search.

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?

Explicitly recommends using this before responding to a ticket to understand history. Explains when to use each parameter (email vs. organization). Does not explicitly state when not to use or name alternatives.

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