fetch_resources_summary

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

No annotations provided, so description carries burden. It describes return structure and error field but lacks details on side effects, permissions, or rate limits. Adequate for a read operation but not comprehensive.

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?

Description has some redundancy ('Use this to get the summary on resource' then 'Fetch a summary...') and informal phrasing. Structured with bullet points and Args/Returns, but could be more concise.

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 provided but Has output schema true, the description partially describes output but not fully (complianceSummary dict lacks key structure). Adequate for simple tool but missing details.

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 0%, but description adds meaning by labeling id as 'asset run ID' and resourceType as 'Resource type', which compensates well. Also lists Returns section, adding value beyond schema.

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 fetches a summary of resources for a given asset run ID and resource type, listing compliance breakdown. It distinguishes from sibling fetch_resources by suggesting use when total items is high.

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 to use when total items in fetch_resources is high, providing clear context for when to choose this tool. Does not mention other alternatives or exclusions.

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