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

Goes well beyond the annotations: it discloses the upsert/full-replacement semantics ('calling again updates it — every field is replaced, so re-pass conditions/recipients'), silent-skip behavior when conditions are unmet, refusal of non-member ids, all times in UTC, and that recipients default to the caller. This is exactly the context needed given destructiveHint=true plus idempotentHint=true.

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?

Purpose is front-loaded and every block earns its place, but the conditions logic is explained at length in prose and then restated in the schema, and the parenthetical asides accumulate. Slightly heavy, still navigable.

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 an 8-parameter scheduling mutation with an output schema present, the description covers cadence/UTC behavior, replacement semantics, recipient restrictions, condition evaluation, and defaults. Return values need not be described since the output schema exists ('Returns the schedule' suffices).

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?

Despite 100% schema coverage, the description adds meaning the schema cannot: ANY-of-N condition semantics ('mode any'), that conditions are evaluated against that run's result, that target may be 'row_count' or a report aggregation alias, that day_of_week is 0=Sun and weekly-only, and worked examples for both condition forms.

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 + resource (schedule one saved analysis for emailed digest) and immediately scopes it against the sibling notion of reports: dashboards cannot be scheduled, segments are refused. One schedule per report and the CSV-attachment behavior let an agent distinguish this from run_report/export_report without opening a schema.

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 'When to use' block gives a clear trigger ('email me this every Monday'), an explicit exclusion (dashboards; choose or save a panel as an analysis first), and a constraint (recipients must be workspace members). It does not name the sibling tools an agent might otherwise reach for (run_report, export_report), so it stops short of full alternative routing.

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