tracer-discover

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds context about what is inspected but does not disclose additional behavioral traits (e.g., rate limits, side effects). Given annotations, the bar is lower, and the description provides some value.

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 sentences, concise and to the point, with no redundant or extraneous information. It structure is clear, starting with the core purpose and following with usage guidance.

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?

The description conveys the tool's purpose and typical use, but lacks details about parameter interplay, expected output, or negotiation of the 'intent' values. Given the schema already lists parameters, the description is adequate but not comprehensive, missing opportunities to explain how the parameters map to discovery actions.

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 does not mention any of the five parameters (query, action, intent, resource, component). While the schema provides brief descriptions, they are generic (e.g., 'Search query for intent="search"'). The tool description offers no added semantic guidance for parameter usage, leaving the agent to rely solely on schema.

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's function: discovering Tracer API resources, actions, and execution contracts. It also specifies what it inspects (rule/limit operations, validation payloads, audit filters, endpoints), distinguishing it from execute tools.

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?

Explicitly states when to use: 'Use this before tracer-execute', providing a clear context and purpose. This guides the agent to invoke it during pre-execution discovery.

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