list_captured_sites

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It simply states the listing action without mentioning whether the operation is read-only, whether it reflects live browser state, or any side effects. Given that this is a list operation, the lack of a read-only hint or other context leaves the agent uncertain about the tool's behavior.

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, clear sentence with no redundant words. It is front-loaded with the action and resource, making it easy for an agent to quickly grasp the tool's purpose.

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?

Given the tool's simplicity (no params, no output schema), the description provides adequate context for the agent to understand what the tool does. It could mention the return format or any prerequisites, but for a basic listing tool, the current level of detail is sufficient. No critical missing information for this simple use case.

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 input schema has zero parameters, so there are no parameter semantics to explain. According to the baseline rule for 0 parameters, a score of 4 is appropriate since the description does not need to add parameter-specific information.

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 'List' and states the exact resource: SharePoint Online sites captured from open browser tabs. This clearly distinguishes it from sibling tools like list_groups or list_pages, which focus on different resources.

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 phrase 'captured from open browser tabs' implies the tool is used when the user wants to see sites that have been captured from their browser. However, it does not explicitly mention when to use this over alternatives like get_active_site or set_active_site_from_tab, nor does it provide exclusions. The usage context is implied rather than clearly stated.

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