sp_site_page_read

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

Annotations already indicate readOnlyHint, idempotentHint, and openWorldHint false. The description adds that the operation is read-only and returns JSON with canvasLayout, providing useful context beyond annotations. However, it does not disclose error handling or rate limits, which is acceptable given the low complexity.

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 extremely concise with two sentences. The first sentence defines the core functionality, and the second adds a critical usage hint (URL format). No unnecessary words 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?

Given the tool has only one parameter, annotations covering safety, and an output schema (implied by 'as JSON'), the description is largely complete. It could be slightly improved by mentioning what happens on error or specifying that the return includes web parts, but overall it sufficiently covers the tool's purpose.

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 single parameter page_url has 0% schema description coverage, so the description fully compensates by providing a concrete URL shape: 'https://<host>/sites/<name>/SitePages/<page>.aspx'. This adds significant meaning beyond the schema's simple string type.

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 clearly states the tool fetches a single SharePoint Page including canvasLayout as JSON. It specifies the verb 'Fetch' and the resource 'a single SharePoint Page', and distinguishes from sibling tools like sp_site_page_list by focusing on a single page with detailed content.

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 description implies usage for retrieving a single page's content by providing a URL format, but does not explicitly state when to use this tool versus alternatives like sp_site_page_list or sp_search_query. No guidance on exclusion criteria or prerequisites is provided.

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