dataverse_list_web_resources

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

Annotations already indicate readOnlyHint=true, idempotentHint=true. The description adds value by detailing the returned fields (webresourceid, name, etc.) and explaining that content is excluded and why, which goes beyond the annotations.

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 concise, well-structured with enumerated output fields and clear filtering options. Every sentence adds value without redundancy, making it easy for an AI agent to parse.

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 complexity (list with filters) and the existence of an output schema, the description covers all necessary aspects: purpose, filters, exclusions, and post-use actions. It is complete and self-contained.

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 has descriptions for each parameter, but the tool description adds further context: it lists the mapping for web_resource_type values (1=HTML, etc.) and provides an example for name_contains ('new_/'). This enhances understanding beyond the schema alone.

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 explicitly states 'List webresource records in the Dataverse environment' and clearly distinguishes from sibling tool dataverse_get_web_resource by noting content exclusion and directing to that tool for content retrieval.

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 guidance on when to use this tool (for listing without content) and when to use an alternative (dataverse_get_web_resource for included content). It also advises calling dataverse_publish_customizations after modifications, which adds workflow context.

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