get_task_status

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

No annotations provided, so the description bears full burden. It only states it retrieves status, but does not disclose whether it is read-only, requires authentication, has rate limits, or any side effects. Minimal disclosure for a tool that likely queries system state.

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 a single sentence that directly states the tool's purpose with no unnecessary words. It is concise and 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?

No output schema exists, and the description only mentions 'detailed status' without specifying what fields or format the status includes. For a simple retrieval tool, this is adequate but could be improved by hinting at typical contents (e.g., state, exit status). Lacks mention of error conditions or node connectivity requirements.

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 has 100% coverage with both parameters described (node: 'Nom du nœud Proxmox', upid: 'ID unique de la tâche (UPID)'). The description adds no additional meaning beyond the schema, so 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?

Description clearly states 'Récupère le statut détaillé d'une tâche Proxmox' which translates to 'Retrieves the detailed status of a Proxmox task'. Verb 'retrieves' and resource 'detailed status of a Proxmox task' are specific. It distinguishes from sibling list_tasks, which lists tasks, by focusing on a single task's status.

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?

Usage is implied: to get status of a specific task given node and upid. However, no explicit guidance on when to use vs. alternatives (e.g., after list_tasks) or when not to use. Missing prerequisites like needing to obtain upid from another tool.

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