auth_start

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

No annotations are provided, so the description carries full burden. It fully discloses key behaviors: immediate return if valid token exists, effect of force parameter, and that it does not need to be called proactively.

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 a concise paragraph of 5 sentences with no fluff. It is front-loaded with purpose and usage conditions, making it efficient for an AI agent to parse.

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?

For a simple auth flow start tool without output schema, the description covers when to call, behavior, and parameter usage. However, it does not mention what the tool returns (e.g., authorization URL), which could be useful for follow-up actions.

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 100% with good descriptions. The description adds context for the force parameter (when to force re-auth) and clarifies defaults for clientId and tenantId, providing meaningful addition beyond schema.

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 starts the Planner authentication flow, using a specific verb ('Start') and resource ('Planner authentication flow'). It distinguishes from sibling tools that are for Planner operations.

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 explicitly states when to use (only on authentication error or user request) and when not to use (proactively before other tools). It clarifies that other tools automatically use stored tokens, providing excellent usage guidance.

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