Get SharePoint List Item

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

With no annotations provided, the description carries the burden. It clearly states 'Read' indicating read-only behavior, and discloses a required permission (delegated Sites.Read.All). This adds safety-relevant context beyond the schema. It does not cover error handling or response format, but the permission and read-only nature are key behavioral traits.

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 concise and front-loaded with the core purpose. The Chinese intent translations add a bit of length but serve a functional purpose for multilingual support. Overall, it is appropriately sized with no unnecessary repetition.

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 read tool with 4 parameters and no output schema, the description covers the essential aspects: what it does, the permission requirement, and a hint at return fields. It does not detail optional parameter behavior (fieldNames), but the schema compensates. The sibling context and lack of output schema mean the description is nearly 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 the baseline is 3. The description does not add meaningful parameter details beyond what the schema already provides; 'and its fields' loosely hints at fieldNames, but the schema already explains that parameter. The description adds minimal extra value here.

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 states 'Read one SharePoint list item and its fields' with a specific verb ('Read') and resource ('SharePoint list item'). It clearly distinguishes this from sibling tools like sharepoint_list_list_items (listing multiple items) and sharepoint_update_list_item (updating). The Chinese intents reinforce the purpose for multilingual queries.

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 clearly implies usage for retrieving a single list item by ID ('Read one'), which contrasts with listing tools. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to select this over bulk or mutation tools.

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