getCustomerDailyStreakProgress

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

With no annotations, the description carries full burden for behavioral disclosure. It only says '🔒 Get streak' – the lock emoji is ambiguous and does not clarify side effects, auth requirements, or return behavior. No useful behavioral information is provided.

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 extremely short, but this is under-specification rather than conciseness. It consists of a vague phrase and an emoji, with no meaningful structure or information. The brevity does not help because it omits critical details.

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 the tool's complexity (2 required parameters, no output schema, no annotations), the description is completely inadequate. It does not explain what the tool returns, any usage constraints, or how it fits into the larger set of customer progress tools. The lack of any explanatory content makes it nearly unusable for an agent.

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 description adds no meaning to the parameters. Schema coverage is only 50% (campaignId has a brief 'campaign Id' description, customerId has none), and the description does not compensate for the missing parameter information. It fails to explain what each parameter represents or how they affect the operation.

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 'Get streak' is a tautology that essentially restates the tool name 'getCustomerDailyStreakProgress'. It fails to specify that this is about daily streak progress or to distinguish it from sibling tools like getCustomerTierProgress or getCustomerStampsProgress.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or scenarios where this tool is appropriate, leaving the agent without direction.

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