Browse SharePoint Drive Children (Deprecated)

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds the deprecation status, which is beyond annotations, but does not disclose return format or behavior on invalid paths. No contradiction with 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, front-loaded sentence with the deprecated flag. It is concise and contains no unnecessary words.

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?

The tool is simple with strong annotations and full schema coverage, but the description omits return value details and any alternative tool recommendation. This is a clear gap, especially for a deprecated tool, but the essential purpose is still communicated.

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 100%, so each parameter has a description. The tool description adds minimal meaning beyond the schema, only restating the action. Baseline 3 is appropriate since the schema carries the parameter details.

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 'Browse files/folders within a SharePoint drive path', providing a specific verb and resource. This distinguishes it from sibling tools like `lyzr_kb_sync_browse_sites` and `lyzr_kb_sync_browse_drives`, and the [deprecated] tag adds context.

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?

No guidance is given on when to use this tool versus alternatives. The [deprecated] tag implies it should not be used, but no replacement tool is recommended. There is no mention of valid use cases or exclusions.

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