Create a search job (primitive)

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

The description discloses behavioral traits: async creation, keepalive polling, and cleanup requirement. However, the annotations set readOnlyHint=true, contradicting the description's claim that it creates a job (a mutation). This is a serious inconsistency.

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 two focused sentences covering action, behavior, lifecycle, and parameter constraints. No unnecessary words; 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?

Given 6 parameters, 1 required, no output schema, the description covers the job lifecycle (create, keepalive, page, delete), time range options, and notes on polling. It lacks explicit mention of the return format or error cases, but is otherwise thorough.

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 100% schema coverage, baseline is 3, but the description adds value: explains `last` units (s/m/h/d), `from`/`to` formats (ISO-8601 or epoch ms), mutual exclusivity, and practical tips like `byReceiptTime` for recent windows. It enhances understanding beyond schema descriptions.

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 action: 'Creates a search job and returns its id WITHOUT waiting.' It distinguishes from siblings like sumo_get_messages, sumo_get_records, and sumo_delete_search_job by being the initiation step that returns immediately.

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 explicit guidance: page with sumo_get_messages/sumo_get_records, delete with sumo_delete_search_job, and time range constraints (exactly one of `last` or both `from`/`to`). It lacks direct comparison with alternatives like sumo_run_search but still gives clear context.

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