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

Annotations already declare readOnlyHint=true, and the description confirms a read operation with 'List'. However, it does not disclose any additional behavioral traits such as pagination behavior (cursor-based being used via page_cursor), rate limiting, or potential empty results. With annotations covering safety, a score of 3 is appropriate as the description adds minimal extra behavioral context.

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?

The description is extremely concise, consisting of a single sentence that states the action and resource, followed by the endpoint. Every word is purposeful, and the critical information is front-loaded. There is no ambiguity or unnecessary detail.

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?

Given the lack of an output schema, the description should ideally indicate what the response contains. It does not mention the structure of the returned list (e.g., job objects with fields). For a listing tool with four parameters, this omission limits completeness. However, the sibling context (other list tools) suggests that response details may be obvious from the resource name, partially mitigating the gap.

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 baseline is 3. The description does not add any additional meaning beyond what the schema provides for the four parameters. For example, it does not explain the relationship between page_size and page_cursor or their format. No extra value is added.

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 clearly states the verb 'List' and the resource 'cron/scheduled jobs on a server', providing specificity. Among sibling tools with similar list operations (e.g., forge_list_databases, forge_list_sites), this tool is uniquely identified as listing scheduled jobs, distinguishing it effectively.

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 does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. While the purpose is clear, there is no comparative context or exclusions, leaving the agent to infer usage based solely on the tool's name and basic description.

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