fetch_resource_types

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

Discloses pagination behavior, retry strategy on timeout, and return of totalPages. Without annotations, it covers key behavioral aspects but omits details like idempotency or caching.

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 well-structured with clear steps and bullet points. It is somewhat verbose but each part adds value, especially the numbered pagination process.

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?

Covers prerequisites, input, output, and pagination workflow. Given the presence of sibling tools and no output schema in structured form, the description compensates well.

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?

Explains each parameter's purpose and pagination usage. However, there is a contradiction: schema default for pageSize is 0, but description suggests starting at 50, which could confuse agents.

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 it gets resource types for a given asset run ID. The verb 'Get' and resource 'resource types' are specific, and it distinguishes from siblings like fetch_resources and fetch_resources_summary.

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?

Provides clear guidance on using fetch_assets_summary to obtain the ID, and detailed pagination steps. However, it lacks explicit mention of when not to use this tool versus alternatives.

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