get_crontab_tasks

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

No annotations exist, so the description carries full burden. It mentions SSH but does not disclose behavioral traits such as authentication methods, error handling, handling of new host keys, timeout behavior, or output format (beyond 'crontab -l output'). This is insufficient for an agent to anticipate behavior.

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 at one sentence (16 words). However, it omits critical details, making it under-specified. It is not overly verbose but fails to earn its place by providing sufficient guidance.

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 tool's complexity (7 parameters, no schema descriptions, no annotations), the description is incomplete. It does not cover authentication, SSH details, output schema interpretation, or error conditions. The presence of an output schema does not compensate for missing usage and behavioral context.

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 0%, and the description adds no meaning to any of the 7 parameters. It does not explain host, user, port, password, key_path, timeout, or accept_new_hostkey. The agent receives no semantic clues about parameter usage beyond the schema types.

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 'collects', the resource 'crontab -l output', and the context 'from a remote Linux host via SSH'. It uniquely identifies what the tool does and distinguishes it from sibling tools which are other system inspection utilities.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites (e.g., SSH access, user permissions), and no exclusions. An agent would not know if this is the right tool for the task.

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