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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real behavioural detail beyond them: a 100-item truncation cap, an ownership filter excluding colleagues, and that a failed run's error is surfaced. It stops short of auth requirements or pagination mechanics, so it is strong but not exhaustive.

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?

Front-loaded with the action and scope in the first sentence, then routing constraints. The enumeration of schedule kinds is dense but each item earns its place by disambiguating siblings; the third sentence's trigger-vs-schedule distinction is the only part that could be tightened.

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 no output schema, the description correctly compensates by describing the return payload (timetable, enabled state, next/last run, last error). Combined with the scope limits and the sibling routing, an agent has everything needed to call this correctly.

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 single parameter (projectId) is fully documented in the schema at 100% coverage, and the description does not restate or extend its meaning beyond the org-wide scope it already implies. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('List your own schedules') and then enumerates exactly which objects count (dashboard emails, alerts, notebook runs, repeated agent runs), which is critical for disambiguating from the many sibling list_* tools. It also names the field each item carries (scheduleId) and who consumes it (fastero_set_schedule_enabled).

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?

Explicitly scopes usage ('your own schedules', 'colleagues' schedules are not', 'the 100 newest are listed') and routes the agent away from this tool when the object is actually a trigger: 'A Python project's schedule, and a dashboard's automatic refresh, are triggers instead, in fastero_list_triggers.' That is a named alternative plus the condition that selects it.

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