list_site_lists

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

No annotations are provided, so the description carries the full behavioral burden. 'List all lists' implies a read-only, non-destructive operation, but nothing is said about pagination, throttling, permission requirements, or what happens with very large sites — meaningful omissions for a tool with zero annotation coverage.

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?

A single front-loaded sentence with no filler or redundancy. It is appropriately sized, though it is minimal to the point of omitting useful context that would not have cost brevity.

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?

With one required parameter, no annotations, and no output schema, the definition is barely sufficient. It does not describe the shape of the returned lists (IDs, titles, templates) or result limits, which an agent needs to chain this into follow-up calls.

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% for the single site_id parameter, so the baseline of 3 applies. The phrase 'in a SharePoint site' merely restates the parameter's role and adds no format, source, or discovery guidance beyond the schema.

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 gives a specific verb (List) and resource (lists in a SharePoint site), which is distinct from list_sites (sites), list_site_drives (drives), and list_site_permissions (permissions). It is clear what the tool returns, but it never names those siblings to draw the boundary explicitly.

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 versus alternatives such as list_sites or get_site, and no prerequisites or exclusions are stated. The required site_id implies the caller must already know a site ID, but the description does not say to resolve one first via list_sites or get_site.

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