create-todo-linked-resource

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

Annotations already indicate destructive intent. The description confirms creation behavior and provides an example but does not add further behavioral details (e.g., permissions, limits). No contradiction with annotations.

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 mostly concise with a tip, though some redundancy exists between the first sentence and the tip. Front-loaded with key action.

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?

Explains purpose and body structure, but does not clarify the meaning of path parameters (todoTaskListId, todoTaskId) or specify that the created object is returned (no output 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?

Schema coverage is 80%, and the description adds a concrete example body structure ({ webUrl, applicationName, displayName, externalId }) that illustrates typical usage, going beyond the schema's property descriptions.

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 it creates a linkedResource to associate a task with a partner application item. The example of linking to an Outlook email is specific and distinct from sibling tools like create-todo-task or list-todo-linked-resources.

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 implies usage for linking tasks to emails/files/web pages via 'Use to link...' but lacks explicit guidance on when not to use or comparisons with alternatives like create-todo-task.

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