get-planner-task-details

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

The description confirms the read-only nature ('Retrieve') and adds useful behavioral context about the @odata.etag response field, which is critical for subsequent updates. Annotations already declare readOnlyHint=true, so the description enhances transparency without contradiction.

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 two concise sentences: the first states the core purpose, the second adds a valuable tip. No redundant information, and the key point is 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?

Given 6 parameters and no output schema, the description provides sufficient context: it explains the tool's role and the crucial ETag detail needed for update workflows. It lacks details about relationships but is adequate for a read-only details retrieval.

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?

All parameters have descriptions in the schema (100% coverage), so the description does not need to add param details. The tip mentions includeHeaders but that is already documented. No additional parameter semantics are provided, earning a baseline 3.

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 action 'Retrieve' and the resource 'plannerTaskDetails object', making the purpose explicit. It distinguishes from sibling tools like get-planner-task or get-planner-plan.

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 tip about @odata.etag being required for update-planner-task-details provides guidance on when to use this tool in conjunction with an update. However, it does not explicitly state when not to use it or provide alternatives.

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