vsphere_list_tasks

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds behavioral context by noting results are 'newest first' and by indicating the tool helps observe environment changes and operation outcomes. This goes beyond the annotations and adds interpretative value.

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 and well-structured: a one-sentence summary, a brief usage note, and a clear Args list. Every sentence earns its place, and the formatting makes key information easily scannable.

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 is a read-only list operation, annotations confirm safety, and an output schema exists (so return format doesn't need explanation), the description covers purpose, usage, and all parameters. It is complete for an agent to select and invoke 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 description includes an 'Args:' block that explains all five parameters (entity, entity_type, hours, states, limits) with clear descriptions. Although the schema itself has no descriptions (0% coverage), the tool description fully compensates by documenting each parameter's meaning and purpose.

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 opens with 'List recent vSphere tasks, newest first,' using a specific verb and resource with clear ordering. It distinguishes itself from siblings like vsphere_get_task (single task) and vsphere_list_running_tasks (filtered to running), making the tool's purpose unambiguous.

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: 'Use this to see what changed in the environment and whether an operation someone else started succeeded.' This gives clear context, though it does not explicitly name alternatives or when not to use it. The guidance is strong but stops short of full exclusion criteria.

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