create-todo-linked-resource

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

Annotations indicate it is a write operation (readOnlyHint=false, destructiveHint=true). The description adds context about the body structure but no additional behavioral details such as authentication or rate limits. With annotations present, a score of 3 is appropriate.

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 paragraphs with a tip. It is front-loaded and concise, though the tip partially repeats the purpose. It efficiently conveys the needed 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?

The description covers the main purpose and provides a sample body. Required path parameters are explained by schema. No output schema exists, but the overall context is sufficient for a standard create operation. Missing explicit mention of response, but acceptable.

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 description includes a tip with a sample body: { webUrl, applicationName, displayName, externalId }, which adds concrete usage guidance beyond the schema's parameter descriptions. Schema coverage is 80%, so the description compensates well.

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 tool creates a linkedResource to associate a task with a partner app item, with a concrete example (Outlook email). It distinguishes from sibling tools like 'delete-todo-linked-resource' and 'create-todo-task'.

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 clear context: 'Use to link tasks to emails, files, or web pages for context.' It does not explicitly state when not to use it or compare to alternatives, but the use case is well-defined.

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