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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully carried by structured data. The phrase 'no spend' adds a small billing-related reassurance not literally in the annotations, but nothing is said about permissions, the date-range window semantics, or what the returned schedule looks like. The 'Fields: soclo://...' pointer is opaque rather than explanatory.

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?

It is short and front-loaded, which is good, but the trailing 'Fields: soclo://tools/soclo_ads_get_campaign_ad_schedule' string is an unexplained artifact that consumes space without conveying anything an agent can act on, while far more important parameter semantics are omitted.

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?

There is no output schema, six parameters (two required, one nested object), and no annotations covering return shape, yet the description gives no indication of what a returned dayparting schedule contains or how fromDate/toDate/windowDays interact. For a read tool of this structural complexity, the definition is too thin to call it confidently.

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% (confirm, requestId and adAccountId documented; platform and accountId bare), and the nested parameters object with campaignId, fromDate, toDate, windowDays and includePerformance is entirely undocumented in the schema and untouched by the description. With coverage below the 80% threshold, the description was expected to compensate for date formats, the meaning of windowDays vs. fromDate/toDate, and the includePerformance flag — it does none of this.

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 specific verb and resource — 'Read a campaign's ad schedule (dayparting)' — matching the title and making clear it is a read operation on a campaign's dayparting. It is distinguishable from the mutating sibling soclo_ads_update_campaign_ad_schedule, though it never names that sibling 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 only usage signal is the terse 'Read only; no spend', which restates the read-only nature without saying when to reach for this tool instead of soclo_ads_get_ad_campaign_details, soclo_ads_get_campaign_targeting, or the update_* counterpart. No prerequisites, no exclusions, no alternative routing.

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