list_checks_by_service

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

No annotations are provided, so the description must disclose behavior. It describes the return format as a dictionary mapping check IDs to check information, but it does not mention potential side effects, authentication needs, or rate limits. The tool is a simple list operation, so the description is adequate but not rich.

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 extremely concise with a single-sentence purpose followed by short args and returns sections. It is front-loaded and free of unnecessary words, earning its place with every sentence.

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's simplicity (single parameter, output schema provided), the description adequately covers purpose, parameter semantics, and return structure. However, it lacks guidance on error conditions or usage context, which would make it fully 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?

The input schema provides only the parameter name and type with no description. The description adds meaning by stating 'Filter by service name (e.g., 'GuardDuty', 'CloudTrail', 'IAM')', giving examples that help the agent understand valid values. This compensates for the zero schema description coverage.

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 'Get all checks filtered by service', which is a specific verb and resource. It further specifies the filtering criterion, distinguishing it from sibling tools like 'list_checks_by_account_type' and 'describe_check'.

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 when needing checks for a specific service but does not explicitly state when to use this tool versus alternatives like 'list_checks_by_account_type'. There is no guidance on when not to use it or mention of prerequisites.

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