get_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Get a list' and provides no information about error handling, permissions, or what is returned. For a read operation, there is no disclosure of side effects (none expected), but the lack of context leaves the agent guessing about failure modes such as 'list not found.'

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 no unnecessary words. It is front-loaded with the verb and resource, making it easy to parse. This is appropriate for a simple getter tool.

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 tool with one parameter, no output schema, and no annotations, the description is minimally sufficient but lacks context. It does not explain what a 'list' refers to in SharePoint, what the return value looks like, or how this tool relates to the many sibling tools (e.g., list_lists, get_item). The absence of error behavior or usage guidance makes it incomplete for an agent deciding whether to invoke it.

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 a single required parameter (listId) with a type and minLength but no description. Schema description coverage is 0%, so the description must compensate. It does not mention listId at all, though the tool name and the phrase 'a list' implicitly suggest the ID identifies which list. The parameter name is somewhat self-explanatory, but the description adds no explicit semantic value.

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 uses a specific verb ('Get') and resource ('a list') and scopes it to 'the active SharePoint site.' This clearly indicates a read operation for a single list. It is not fully explicit about retrieval by ID, but the tool name and sibling presence (list_lists) imply a single-get vs. list-all distinction.

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. No mention that this retrieves a single list by ID, nor any reference to list_lists for enumeration or get_item for list items. The description simply states what it does without usage context.

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