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

The annotations already declare this read-only and non-destructive, so the safety profile is known. The description adds no behavioral context beyond that, such as whether it returns all records, pagination behavior, or ordering, so it does not enrich the 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 a single, front-loaded sentence with no filler or redundant wording. For a zero-parameter list tool, five words are appropriately sized 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?

With no parameters, annotations covering the safety profile, and an output schema that can describe the return shape, the minimal description is mostly sufficient. The only gap is that it does not explicitly say it returns all inbound assistants or mention the single-record alternative, but those are easily inferred from the name and sibling tools.

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?

The tool has zero parameters, so the description cannot reasonably add parameter-level semantics. The baseline for a 0-parameter tool is 4, and no further explanation is needed here.

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 uses a specific verb ('list') and a specific resource ('inbound assistants'), making the action and object clear. The 'inbound' qualifier distinguishes it from sibling tool list_outbound_assistants, and 'list' separates it from get_inbound_assistant, though it stops short of stating any scoping or return details.

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?

Usage is implied by the naming convention and sibling tools: an agent can infer that this lists inbound assistants rather than a single one or outbound ones. However, there is no explicit when-to-use or when-not-to-use guidance, and no mention of preferring get_inbound_assistant for a single record.

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