sp_site_followed_list

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

Adds important auth limitation (not available in service-principal mode) and confirms read-only nature beyond what annotations provide. No contradiction with annotations.

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?

Three concise sentences, front-loaded with the main action. Every sentence adds value without redundancy.

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 parameterless list tool with output schema, the description covers purpose, usage context, auth limitation, and safety, making it 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?

No parameters, so description does not need to add parameter details. Baseline 4 applies; the description implicitly covers the user context.

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?

Description clearly states 'List sites the signed-in user has marked as Followed' with specific verb and resource. It distinguishes from guessing site URLs and positions itself as a curated entry point, differentiating from siblings like sp_site_list or sp_search_query.

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 says it's useful as a 'my SharePoint' entry point and notes unavailability in service-principal auth mode. While it does not name alternative tools directly, the context is clear about when to use this tool.

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