sharepoint_read_file

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

Discloses read-only nature (no import), supported formats, and truncation behavior (max_chars). With no annotations, it carries the full burden well, though could mention authentication or error handling.

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?

Four sentences, no fluff. Front-loaded with core action, then use case, formats, and alternative. Every sentence 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?

Covers key aspects: action, use case, alternative tool, supported formats, truncation. Lacks mention of error handling or permissions, but given output schema exists, it's reasonably complete.

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 baseline is 3. Description adds minor context about path relativity and max_chars truncation, but does not significantly enhance 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?

Clear verb 'lit' (reads) and resource 'fichier SharePoint', explicitly states it does not import into Cleyrop, distinguishing it from sibling tool transfer_sharepoint_to_cleyrop.

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 states when to use (for analysis, summarization, querying directly) and when not to (for permanent copying, use transfer_sharepoint_to_cleyrop).

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