Read an enrollment timeline

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world. The description adds genuinely new context: required scope campaigns:read / luca:read, data sensitivity full_content, and explicit workspace override semantics. It doesn't restate the return shape, but the output schema carries that, so this is solid added value.

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?

Front-loaded purpose sentence followed by terse, scannable metadata lines (operation, scopes, idempotency, workspace override). No filler, and the most important information leads.

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?

An output schema exists, so return-value documentation is not required, and the description covers scopes, sensitivity and workspace targeting. For a read-only nested-resource lookup the coverage is nearly complete, with only the identifier semantics left implicit.

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 description coverage is 50%; the two workspace params carry schema descriptions while id and enrollmentId do not. The description's workspace-override sentence meaningfully explains workspaceId/workspaceSlug but leaves the two UUID identifiers to inference ('one enrollment'). Baseline 3 is appropriate.

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 states a precise verb and resource: 'Read every step one enrollment has been through: what got sent, when, and how the lead responded.' The scope ('one enrollment' vs. the list-oriented sibling luca_campaigns_enrollments_list) is unambiguous, and an agent can tell what it returns without opening the schema.

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 phrasing ('one enrollment') but the description never states when to choose this over luca_campaigns_enrollments_list or luca_leads_explain, nor any exclusions. It adds only the workspace-override note, which is configuration, not selection guidance.

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