Get analytics for one pin

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the required OAuth scope ('pins:read'), which is genuinely useful auth context not present in the annotations. It does not mention rate limits or what a partial/failed window returns.

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 tight sentences with zero filler; the resource and window constraint are front-loaded, and the auth scope is appended as a short clause. Nothing could be trimmed without losing content.

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 read-only analytics fetch with a fully documented schema and no output schema, the description covers the essentials: single-pin scope, window bound, and required scope. It stops short of clarifying what 'daily' granularity returns or how split/metric parameters shape the response.

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 schema already documents all seven parameters including the date constraints, enum values, and metric list. The description's only added parameter-relevant fact is the 90-day window, which the schema already states for both dates. Baseline 3 applies.

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?

Specific verb+resource: 'Daily analytics for a single pin over a date window of up to 90 days.' The word 'single' implicitly distinguishes it from sibling pinterest_get_multi_pin_analytics and pinterest_get_user_analytics, though no sibling is named explicitly.

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 states scope ('single pin', 'up to 90 days') but gives no when-to-use guidance, no conditions that route the agent to get_multi_pin_analytics or get_user_analytics, and no exclusions. Usage must be inferred from the tool name alone.

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