get-tasks

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, so the description's claim of 'Get tasks' aligns. However, the description adds minimal behavioral context beyond annotations (e.g., no mention of pagination, rate limits, or return structure). It is adequate but not enhanced.

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 very concise with two sentences: the first states the core purpose, the second adds clarifying context about tasks vs. checklist items. No extraneous words, and it is front-loaded with the essential information.

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 7 parameters with full schema descriptions and readOnlyHint but no output schema, the description is minimal. It does not explain the return format or how to use OData query parameters. For a tool with moderate complexity, it is somewhat incomplete, but acceptable for a simple read operation.

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% for all 7 parameters, so the baseline is 3. The description does not add additional meaning or usage examples beyond what the schema already provides. Parameters like filter, orderby, select have descriptions, but the tool description does not elaborate on typical usage or constraints.

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 (Get) and resource (tasks) and specifies the scope (from a specific Microsoft Todo list). It distinguishes tasks from checklist items, which are sibling tools, and clarifies the hierarchical relationship. This provides strong purpose clarity.

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 does not explicitly state when to use this tool vs alternatives, nor does it mention prerequisites or when not to use it. While the sibling tools are listed, there is no guidance on selecting this tool over others like get-task-lists or create-task. This is a gap.

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