get_view_formatting

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

No annotations are provided, so the description carries the full burden. 'Get' implies a read operation, but the description does not disclose any additional behavioral details such as permissions required, error handling, or the structure of the returned JSON. It adds little beyond what the tool name already suggests.

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 sentence of ten words, front-loaded with the verb and resource. Every word is informative, with no fluff or 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?

This is a simple read tool with two parameters and no output schema, but the description is too sparse. It does not explain what 'JSON formatting' means, what the return value contains, or how this tool relates to formatting updates. The lack of annotations and output schema makes this description insufficient for a fully autonomous agent.

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 schema has 0% description coverage, and the description does not explain listId or viewId. While the parameter names are intuitive in a SharePoint context, the description fails to compensate for the missing schema documentation, leaving the agent to guess the expected format or relationship between them.

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 'Get JSON formatting for a SharePoint list view' clearly states the action (get) and the resource (JSON formatting for a view). It distinguishes itself from sibling tools like get_column_formatting and preview_view_formatting_update, which operate on columns or perform updates rather than reads.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that it is for reading current formatting, nor does it point to preview_view_formatting_update or apply_view_formatting_update for modifications. The agent must infer usage purely from the name.

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