Consulter une tâche par son ID

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

With no annotations provided, the description carries full burden but only mentions 'avec un rappel si nécessaire' as behavioral context. It lacks details on permissions, rate limits, error handling, or what 'rappel' entails (e.g., notification type). This is insufficient for a tool with potential side effects like reminders.

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 a single, efficient sentence that front-loads the core purpose. However, the vague phrase 'avec un rappel si nécessaire' adds minimal value and could be more precise, slightly reducing conciseness.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what details are returned (e.g., status, metadata) or the reminder mechanism, leaving significant gaps for a tool that retrieves task details and potentially triggers reminders.

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 description coverage is 100%, with the single parameter 'id' fully documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 without compensating value.

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 states the verb ('Récupère' - retrieves) and resource ('détails d'une seule tâche' - details of a single task), making the purpose specific. However, it doesn't explicitly differentiate from sibling tools like 'task_history' or 'task_logs' which might also retrieve task-related information, preventing a perfect score.

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 minimal guidance with 'avec un rappel si nécessaire' (with a reminder if necessary), which hints at optional behavior but doesn't clarify when to use this tool versus alternatives like 'task_history' or 'task_logs'. No explicit when/when-not rules or sibling comparisons are included.

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