fetch_sysdig_plan

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

No annotations provided. Description discloses the need for an environment variable and describes fleet summary behavior. It implies a read-only fetch operation but does not explicitly state whether the tool has side effects or other behavioral constraints (e.g., rate limits, data modification).

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?

Extremely concise: two sentences clearly state the core action, required environment variable, and a notable behavior (fleet summary). No wasted words.

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?

With no output schema, description should provide expectations about the plan output, but it only mentions fleet summary. Does not cover error cases, response format, or other important context for a tool that generates plans. Could be more complete.

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 75%, so baseline is 3. Description adds no additional insight beyond what the schema already provides for each parameter. The term 'multiple workloads' is mentioned but not tied to a specific parameter.

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?

Description clearly states it fetches runtime scan results and generates remediation plans, with a specific mention of fleet summary for multiple workloads. Distinguishes from sibling tool 'generate_remediation_plan' by implying it both fetches and generates.

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 mentions required environment variable (SYSDIG_API_TOKEN) and describes special behavior for multiple workloads. However, does not explicitly state when to use this tool versus the sibling or when not to use it.

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