send_daily_summary_now

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

Annotations already signal a non-read-only, non-idempotent action, so the mutation side effect is known. The description adds useful behavioral context: the recipient comes from RECIPIENT_EMAIL in the .env and no email prompt will be shown. However, it does not mention whether fresh data is gathered at call time, whether repeated calls send duplicate emails, or what the return/result behavior is. This is acceptable but not rich.

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?

Two concise sentences convey purpose, contents, recipient source, and the no-prompt behavior with no filler. The core action is front-loaded, and every clause adds relevant information.

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?

For a zero-parameter send action, the description supplies everything an agent needs: what email is sent, what data it includes, who receives it, and that it runs immediately without prompting. No output schema exists, but return value explanation is not essential for this simple trigger.

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?

With zero parameters but full schema coverage, the baseline is 4. The description goes beyond the empty schema by explaining the absence of interactive parameters: recipient is predetermined via RECIPIENT_EMAIL from .env and no prompt is needed. This fully addresses why an agent can call it without arguments.

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 action ('Send the daily system summary email') and the exact resource, with a clear temporal qualifier ('right now'). The included content list (CPU, memory, vnstat network stats, top processes) makes the tool's scope unambiguous and distinguishes it from generic email-sending siblings like send_test_email.

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 makes the usage context explicit: it triggers an immediate daily summary rather than waiting for a scheduled run. It also clarifies there is no interactive email prompt, so an agent knows it can be invoked non-interactively. It does not explicitly name alternative tools or conditions for avoiding it, but the context is clear enough for a 0-parameter tool.

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