Read the coach's niche profile

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context (required scopes coach:read, OAuth scope luca:read, data sensitivity redacted), but 'Does not require idempotency' merely restates the idempotentHint annotation and no return/pagination behavior is described.

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 lead sentence front-loads the resource and its contents before any operational boilerplate. The scope/endpoint scaffold lines are somewhat mechanical and one line duplicates the annotations, but the whole remains short and skimmable.

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 an output schema present, return values need not be described, and annotations plus the auth/scope lines cover the operational surface. The one meaningful gap is that nothing separates this tool from luca_coach_niche, an agent-facing ambiguity.

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 100%, so the baseline is 3. The description lifts it by explaining that workspaceId/workspaceSlug override the workspace configured by environment — a detail the schema's terse 'Optional Luca workspace id override' does not clarify.

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 and resource ('Read the coach's niche profile') and enumerates what the profile contains (offer, audience, price range, promised outcomes, disqualifiers, FAQs), plus the underlying GET endpoint. However, it never distinguishes itself from the near-identical sibling 'luca_coach_niche', leaving an ambiguity an agent must resolve on its own.

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?

'This is the context that decides whether a lead is a fit' implies a use case, and the closing line explains how to override the default workspace. But there is no explicit when-to-use/when-not guidance and no named alternative, which matters given siblings like luca_coach_niche and luca_coach_objection_playbook.

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