Link a tracker

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

Annotations already indicate readOnly=false, destructiveHint=false, but the description adds valuable behavioral context: the previous state is snapshotted before the write and can be reverted with nuvio_undo. This goes beyond annotations and helps the agent understand side effects and recovery.

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 short and front-loaded with the main purpose, followed by usage condition and revert note. It is efficient but could have added a little more parameter context without becoming bloated.

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 complexity (7 params, no output schema, write operation), the description covers the key behavioral aspects: purpose, usage condition, and revert path. However, it omits parameter semantics for the non-obvious params (refresh_token, tracker_user_id, expires_in_seconds), which would help the agent build correct calls.

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 only 14%, so the description should compensate, but it doesn't explain individual parameters beyond 'tracker OAuth tokens' and 'profile'. The schema already provides basic parameter descriptions for 'tracker' and 'access_token' but most parameters (username, profile_id, refresh_token, etc.) lack description in both schema and tool description. The description adds general context but not per-parameter meaning.

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 stores tracker OAuth tokens for a profile, with a specific verb ('Store') and resource ('tracker OAuth tokens'). It also distinguishes from the normal sign-in flow and mentions the sibling undo tool.

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?

It explicitly says 'Use this only when tokens were obtained out-of-band; prefer the app sign-in flow.' This is a clear when-to-use and when-not-to-use instruction, and it names the alternative flow even though not a sibling tool.

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