List Sumo Logic Monitors (native alerting; read-only)

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

Annotations already indicate readOnlyHint=true, but the description adds value by stating 'no search jobs involved' and warning about HTTP 403 if lacking the 'View Monitors' capability. This goes beyond the annotation, though it doesn't cover pagination or rate limits.

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, no redundancy. Every word serves a purpose: it defines the tool's output, operational nature, auth requirement, and filter options. Excellent front-loading.

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 simple listing tool with two optional parameters, the description covers return fields, auth requirements, and query behavior. No output schema exists, but the description lists the fields returned (name, folder path, etc.). It is complete given the tool's complexity.

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 coverage is 100% (limit and query described), so baseline is 3. The description adds meaning by stating the query filters 'monitor name/content', which is not explicit in the schema's description ('Filter text...'). The limit parameter is well-documented in the schema. Overall, the description enhances parameter understanding.

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 uses specific verbs ('Discovers') and details the resource ('Sumo Logic Monitors' with attributes: name, folder path, type, etc.). It distinguishes from sibling tools by explicitly calling out 'native alerting' and 'read-only management-API call'. The title also reinforces the purpose.

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 implies usage for discovering monitors and states it's a read-only call. While it doesn't explicitly list when-not-to-use or alternatives, the sibling tool names (e.g., sumo_run_search) and the context make the scope clear. The capability requirement provides a boundary for usage.

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