get-planner-task

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

Annotations already declare readOnlyHint=true, so the agent knows it is a safe read operation. The description adds value by mentioning the @odata.etag and includeHeaders parameter, but does not disclose other behavioral traits such as authentication requirements or rate limits. The description provides some context beyond annotations but is not deeply transparent.

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 extremely concise—two sentences with no wasted words. The purpose is stated first, followed by a useful tip. It is front-loaded and every sentence earns its place.

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 read-only nature and good annotations (readOnlyHint, destructiveHint, openWorldHint), the description provides adequate context. It covers the main purpose and the critical etag tip. However, it does not describe pagination or response structure, which might be expected given the absence of an output schema. Still, it is fairly complete for a simple retrieval tool.

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, so the schema already describes all 6 parameters. The description does not add additional meaning beyond the schema; the tip only highlights one parameter (includeHeaders). Baseline 3 is appropriate as the schema carries the load.

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 starts with 'Retrieve the properties and relationships of plannerTask object,' which is a specific verb+resource combination that clearly states what the tool does. It effectively distinguishes from sibling tools like update-planner-task (write) and get-planner-task-details (more specific).

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 suggests using includeHeaders=true to capture the etag for use with update-planner-task, which is a helpful usage guideline. However, it lacks explicit guidance on when to prefer this tool over alternatives like get-planner-task-details, and does not mention when not to use it.

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