fetch_resources

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

With no annotations, the description fully covers pagination behavior, timeout handling, and response structure. It discloses the step-by-step process for paginating through results. Missing details on required permissions or rate limits, but otherwise transparent.

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 verbose, including a lengthy nested return structure and step-by-step pagination list. While structured, it could be more concise. The first sentence is clear, but later sections add redundancy.

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 includes an output schema, which reduces the need for return value explanation, but it still duplicates some information. It covers pagination and timeouts but lacks details on valid values for resourceType and complianceStatus, and error scenarios beyond the error field.

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%, so the description must compensate. It explains page and pageSize semantics through pagination instructions but only provides minimal label-like descriptions for id and resourceType ('Asset run id', 'Resource type'). complianceStatus is not explained at all.

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 resources for given asset run id and resource type', specifying the verb 'get' and the resource. It distinguishes from sibling tools like fetch_resources_by_check_name by emphasizing asset run id and resource type parameters.

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 provides explicit pagination instructions and recommends using the 'summary tool' for large datasets, offering clear guidance on when to use pagination and an alternative. However, it does not directly contrast with all sibling tools like fetch_resources_summary.

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