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 context beyond that: which fields each item carries, that cron is read in UTC, and that the cron lives only here rather than on the Python entrypoint. It does not discuss volume/pagination for a list across the whole org, which is the main remaining gap.

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 scope and enumeration, then returns, then the sibling redirect. Dense and mostly waste-free, though the 'py:<pythonProjectId>:<entrypointId>' naming digression is lengthy relative to how often it matters.

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?

No output schema exists, and the description compensates by enumerating the returned fields (_id, name, type, enabled, cron) and their semantics. Combined with the sibling redirect and the UTC note, an agent has everything needed to call and interpret this tool.

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?

There is a single orgId parameter already documented at 100% schema coverage, including the default behavior, so the schema does the heavy lifting. The description never references orgId, but no additional meaning is needed given the schema text.

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 every trigger in the organization') and enumerates the concrete trigger kinds covered: Python schedules, dashboard/page refreshes, and DB/Kafka/webhook watchers. It also names the distinguishing sibling (fastero_list_schedules) so the boundary is unambiguous.

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 routes the agent: 'Dashboard emails, alerts and notebook runs are schedules instead, in fastero_list_schedules.' It also connects the returned _id to fastero_enable_trigger and fastero_disable_trigger, telling the agent what to do with the output.

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