Validate SharePoint Site Access (Deprecated)

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

Annotations already provide idempotent and non-destructive hints, but the readOnlyHint is false, which is ambiguous for a validation tool. The description adds the deprecation flag but does not disclose return values, side effects, or error behavior, leaving gaps beyond the 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 a single concise sentence with the deprecation warning front-loaded. It is appropriately sized and every word earns its place.

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?

With no output schema, the tool description must explain what the agent can expect in return, but it does not. It also lacks any note about what to use instead (given deprecation) and does not clarify whether validation is per-URL or overall, making the description incomplete for practical invocation.

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?

Both parameters are described in the schema with 100% coverage, so a baseline of 3 is appropriate. The description only paraphrases 'credential' and 'site/drive URLs' and adds no additional format, constraints, or parameter-specific guidance.

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 with a specific verb ('Validate'), a resource ('SharePoint site/drive URLs'), and a credential scope. It also flags the tool as deprecated, which helps an agent distinguish it from current alternatives.

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 gives no guidance on when to use this tool versus the many related sibling tools (e.g., lyzr_kb_sync_browse_sites, lyzr_livesource_ext_validate_access). Despite deprecation, no alternative tool is suggested; the agent is left without usage context.

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