dataverse_list_plugin_trace_logs

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint false. Description adds that records are ordered newest-first and returns trace/exception information. No contradictions, and the additional ordering detail is valuable.

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 is well-structured with clear paragraphs: purpose, return info, useful filters list, and prerequisite notes. Slightly verbose with bullet-like formatting, but front-loaded and efficient overall.

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 complexity of 8 parameters, presence of output schema, and sufficient annotations, the description covers filters, ordering, and prerequisites. It could mention pagination (top parameter behavior), but output schema likely covers return structure.

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?

Despite 0% schema description coverage, the tool description provides detailed explanations for key parameters (e.g., partial match for type_name, examples for hours_ago and message_name, exclusion filter for exceptions_only). This adds significant meaning beyond the schema's parameter names and types.

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?

Description explicitly states 'List plug-in trace log records with optional filters', clearly identifying the verb and resource. It distinguishes from sibling tools like dataverse_get_plugin_trace_log_setting and dataverse_set_plugin_trace_log_setting by focusing on listing logs with filters.

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?

Description provides explicit usage guidance: prerequisite to enable logging via dataverse_set_plugin_trace_log_setting, and how to check setting with dataverse_get_plugin_trace_log_setting. It also lists useful filters, helping the agent decide when to use this tool.

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