hermes_sharepoint_login

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

Discloses the interactive browser sign-in process and automatic token refresh, which is useful behavioral context. Since no annotations exist, description carries full burden, but it does not detail timeout behavior or potential failures beyond the sign-in step.

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?

Two sentences, first sentence states purpose, second gives usage instruction. No redundant information, front-loaded, and efficient.

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 tool with one parameter and no output schema, description covers purpose, usage trigger, and behavioral details (browser sign-in, token refresh). Minor missing aspects like return value or error handling, but overall sufficient.

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 only parameter (timeoutSeconds) is fully described in the schema (coverage 100%). The description adds no additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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?

Description clearly states the tool connects to SharePoint/Microsoft Graph to enable full document content reading. It distinguishes from sibling 'hermes_login' by specifying SharePoint-specific scope.

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?

Explicitly says to call this if 'hermes_get_document_content' indicates it is not configured, giving a clear trigger condition. Lacks explicit when-not-to-use or alternative tools, but the guidance is effective.

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