sharepoint_login_start

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

No annotations are provided, so the description fully discloses behavior: returns a URL, code, and login_id; instructs user to enter code in browser; and directs to call 'sharepoint_login_finish' with the login_id afterward.

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 about 6 sentences, clear and front-loaded with purpose. Slightly verbose with repeated examples but well-structured.

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 no parameters and an output schema (presumably defined), the description covers the login flow, return values, and necessary next step (calling sharepoint_login_finish). No gaps.

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 input schema has zero parameters, so no parameter info is needed. The description adds no param details, which is acceptable. Baseline 4 for no parameters.

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's purpose: starting login/authentication to SharePoint ('Démarre la connexion / l'authentification'). It distinguishes itself from sibling 'sharepoint_login_finish' which is for completing the login.

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 explicit when-to-use instructions: call directly upon user intent to log in, with examples. It tells not to explain steps or ask user to call function. However, it does not mention alternatives like checking auth status first via 'sharepoint_check_auth'.

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