list_my_jobs

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

Discloses automatic decryption of Nostr results, source tagging, and a security warning about untrusted external data. Lacks details on what happens if local file is absent, but overall transparent given no annotations.

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 sentences plus a warning, each providing essential information without redundancy. Purpose is front-loaded, and every sentence earns its place.

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?

Covers key behavioral aspects (local vs Nostr, decryption, source tagging, security) despite no output schema or annotations. Minor omission: no explanation of limit or kind_offset, but defaults make them self-explanatory.

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 description adds value for include_nostr beyond the schema, explaining its use cases. However, limit and kind_offset lack any description, and schema coverage is only 33%, so the description does not fully compensate for all three parameters.

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 lists jobs submitted by the current agent from local history, with optional Nostr merge. This distinguishes it from sibling tools like list_agents or create_job.

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?

Provides explicit guidance on when to use include_nostr (true for external submissions or cache recovery, false for normal use as local cache is source of truth). This helps the agent decide between alternatives.

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