get-planner-task-details

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

Annotations already indicate read-only and non-destructive behavior. The description adds value by revealing that the response includes an ETag necessary for updates, which is not captured by annotations. This provides actionable behavioral insight for agents.

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 consists of two sentences with no extraneous text. The main purpose is front-loaded, and the tip is separated with an emoji for clarity. Every sentence serves a clear purpose.

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?

The description explains what the tool retrieves (properties and relationships) and mentions the ETag in the response. While there is no output schema, the description sufficiently describes the key output aspects. The parameter details are covered in the schema.

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 input schema has 100% coverage with clear descriptions for all 6 parameters. The description adds extra value by highlighting the includeHeaders parameter with a specific use case (obtaining ETag), going beyond the schema's generic description.

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 'Retrieve' and the target resource 'plannerTaskDetails object', including its properties and relationships. This distinguishes it from sibling tools like get-planner-task or get-planner-plan which retrieve different objects.

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 includes a tip that the response contains @odata.etag required for update-planner-task-details, advising to use includeHeaders=true. This gives clear context for when to set that parameter. However, it does not explicitly state alternatives or when not to use the tool.

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