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

Annotations already declare this read-only and non-destructive, so the safety profile is covered. The description adds useful behavioral context beyond the clues: the returned codes/ids are team-scoped and the write tools will reject unknown values, which explains the side-effect context of a read tool meant as a prerequisite. It does not describe errors or pagination, but those are irrelevant here.

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 carry all needed information without any waste: the first lists the three concrete outputs, the second gives the essential call-before context and rationale. The most important information is front-loaded.

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 a zero-parameter input schema, a low-complexity read operation, and an existing output schema, the description is fully adequate. It explains what is returned, that data is team-specific, and how the result should be used before related write calls. Nothing necessary for an agent to invoke it correctly is missing.

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 0 parameters and an empty input schema, so there is no parameter meaning for the description to add. Per the baseline for zero-parameter tools, this is complete enough without any parameter-specific descriptions.

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 opens with an explicit verb and resource ('Read the current team's lead configuration') and lists exactly what is returned: follow-up status codes with label/color/order, the color tag library, and assignable members. It also differentiates itself from the write-related siblings because it is positioned as the read-side lookup.

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?

The description provides explicit when-to-use guidance: call it before update_lead / set_lead_tags / assign_leads. It explains why this ordering matters, since the values are team-specific and the write tools reject unknown values. This is strong routing context for an agent.

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