get_cron_logs

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the basic action. It does not specify what constitutes 'recent', whether logs are system-wide or user-specific, or any prerequisites. The agent lacks context about side effects, scope, or limitations.

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 a single, direct sentence that conveys the purpose with no unnecessary words. It is appropriately sized for a simple retrieval tool.

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?

The tool is simple (one optional parameter) and has an output schema, so the description is minimally complete. However, it leaves ambiguity about the scope of 'system' and the meaning of 'recent', and does not address how to get logs for specific cron jobs (though the tool only supports a line count).

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 schema has full coverage for the only parameter 'lines' with a description, so the baseline is 3. The tool description does not add any additional meaning to this parameter, but the schema adequately documents it.

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 tool retrieves recent cron execution logs, using a specific verb ('Get') and resource ('cron execution logs'). This distinguishes it from sibling tools that manage cron entries, such as list_crontab or add_cron_entry.

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 implies usage for inspecting logs but does not explicitly discuss when to use it versus alternatives. No exclusions or comparison with sibling tools are provided, leaving the agent to infer the use case.

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