search_crontab

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

With no annotations, the description carries the burden. It discloses the case-insensitive matching behavior, which is useful context for an agent. However, it does not mention read-only nature, empty result behavior, or any limitations beyond the literal search semantics. This is minimal but not absent transparency.

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, front-loaded sentence with no filler words. It communicates the core action, target resource, and a key modifier (case-insensitive) efficiently.

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 simplicity (one parameter, output schema present), the description provides sufficient context for an agent to select and invoke it. The main gap is lack of explicit guidance on when to prefer this over list_crontab, but for a one-line search function, this is a minor omission.

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 alone says the keyword is 'Text to search for', but the description clarifies that matching is case-insensitive and uses 'containing' to imply substring matching. This adds meaningful semantic detail beyond the schema, which already covers the parameter name and type.

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 searches crontab entries for a keyword, with case-insensitivity as a key qualifier. It uses a specific verb ('Search') and resource ('crontab entries'), and distinguishes from siblings like list_crontab by implying a filtered search rather than a full listing.

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 intended use case is implied: when you need to find crontab entries containing specific text. However, it does not explicitly mention alternatives or when not to use this tool. No exclusion criteria or comparison to sibling tools are provided, so it remains at the 'implied usage' level.

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