fetch_resources_by_check_name_summary

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

No annotations provided, so description carries full burden. It discloses the return format (compliance summary with breakdown) and that it's a summary, implying no side effects. However, it does not mention pagination behavior or rate limits, which would be helpful but not critical for a fetch operation.

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 somewhat verbose with repeated phrases like 'Use this to get the summary on check resources'. It has bullet points and sections, but could be more concise. The structure is clear but not tight.

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 the tool has an output schema (indicated), the description doesn't need to fully detail returns, but it does include a returns section. However, it fails to document the 'check' parameter and does not clarify pagination details. For a tool with 3 required parameters, the description is incomplete.

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 description coverage is 0%. The description only explains two of three required parameters (id and resourceType) in the Args section, omitting 'check'. This is a significant gap. No format, enums, or constraints are mentioned, leaving the agent uncertain about the 'check' 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?

The description clearly states the tool's purpose: fetching a summary of check resources. It uses specific verbs ('get summary') and resources ('check resources') and distinguishes from the sibling tool 'fetch_resources_by_check_name' by mentioning it's a summary when items are many.

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 says 'Use this when total items in fetch_resources_for_check is high', providing clear context for when to use this tool versus alternatives. Also notes that paginated data is sufficient.

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