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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the resource and return fields; it does not explicitly confirm read-only behavior, mention error cases (e.g., missing page), authorization needs, or any side effects. 'Get' implies a read operation, but that is not stated.

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?

Two short sentences with no filler. The first front-loads the verb and resource; the second lists the return contents, which is useful and directly actionable.

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 one-parameter read tool, the description is moderately complete: it states the resource and output fields, which partially compensates for the missing output schema. However, it lacks alternative-selection guidance and behavioral caveats, so an agent may not know when to choose this over get_page or what happens for invalid/nonexistent pages.

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 already fully describes page_id as a UUID string with 100% coverage. The description adds little beyond 'for a page,' so parameter semantics remain at the baseline for fully covered schemas.

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 and resource ('Get the page summary block for a page') and lists the returned fields (summary, purpose, status, tags, key topics). It is clearly distinguishable from siblings like get_page, which would return more page data, and update_page_summary, which is the write counterpart.

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 gives no explicit when-to-use or when-not-to-use guidance. It does not differentiate from closely related tools such as get_page, get_page_tree, or search_pages, leaving the agent to infer when this tool is preferable.

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