dataverse_list_sdk_messages

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to restate safety. The description adds context that this tool is used for discovery, but does not disclose additional behavioral traits such as pagination, authorization needs, or performance implications. The bar is lower due to annotations, but the description offers no extra transparency beyond what annotations provide.

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 consists of two concise sentences. The first sentence states the core purpose, and the second provides usage context with examples. No redundant or irrelevant information is included, and the key details are front-loaded.

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 tool has an output schema, so the description does not need to explain return values. The description adequately covers when to use the tool and how its output feeds into another tool. Given its simplicity and the presence of annotations, the description is complete and sufficient for an agent to use the tool correctly.

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 detailed descriptions for all parameters (top, filter, select, dataverse_url, name_contains). Despite the context signal of 0% schema description coverage, the actual schema has clear descriptions. The tool description does not add parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 defines the tool as listing SDK messages, which are the catalog of operations plug-in steps can intercept. It distinguishes the tool from its sibling dataverse_get_sdk_message by stating it is used to discover valid message names before resolving a message_id, preventing overlap.

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 explicitly states when to use the tool: to discover valid message names (e.g., 'Create', 'Update', 'Assign') before calling dataverse_get_sdk_message. It provides a clear workflow and implies when not to use it (i.e., not for resolving specific message IDs).

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