Read the post-call deal sync settings

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), and the description adds genuinely non-structured context: required scopes (coach:read, luca:read), that data sensitivity is 'redacted', and the underlying GET endpoint. 'Does not require idempotency' largely restates idempotentHint, but the auth and redaction details are real additions.

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 short and front-loaded: the purpose sentence comes first, followed by a compact operational block. The 'Does not require idempotency' line duplicates the idempotentHint annotation and is the one sentence that does not fully earn its place.

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?

For a zero-required-parameter read tool with an output schema, an idempotency annotation, and full schema coverage, the description supplies everything needed: endpoint, auth scopes, sensitivity handling, and default-workspace override semantics. Return values are covered by the output schema, so nothing material 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?

Schema coverage is 100% (baseline 3), and the description goes beyond the terse schema text by explaining that both parameters override a default workspace configured by the environment. That clarifies the otherwise unstated fallback behavior when neither parameter is supplied, which the schema does not convey.

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?

States a specific verb (read) and resource (post-call deal sync settings: the CRM pipeline and the stage each call outcome maps to), which is more concrete than the title alone. It is reasonably distinguishable from related siblings like luca_coach_post_call_settings and luca_coach_post_call_crm_mapping, though it never explicitly says how it differs from 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?

Usage is implied rather than stated: an agent can infer this is the configuration-inspection tool for post-call deal syncing. The only explicit usage instruction is 'Use workspaceId or workspaceSlug to override the default workspace configured by environment', which is parameter guidance rather than when-to-use/when-not guidance, and no alternative sibling is named.

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