Get Page

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral detail: it specifies exactly what is returned (title, timestamps, parent info) and crucially what is NOT returned (page content). This goes beyond the 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?

The description is exceptionally concise: two sentences, no unnecessary words. The first sentence states the core purpose, and the second adds critical information about what is not included and an alternative. Every sentence earns its place.

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 absence of an output schema, the description provides adequate context: it lists the returned fields (title, timestamps, parent info) and notes what is excluded. It also references the sibling for content retrieval. It is complete enough for a simple read-only tool, but could mention error scenarios or prerequisites.

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 schema description coverage is 100% for the single parameter 'pageId', with description 'The unique identifier of the page'. The tool description does not add any additional meaning or usage details for this parameter beyond the schema. Baseline 3 is appropriate.

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 gets metadata for a specific OneNote page by ID, using a specific verb and resource. It distinguishes itself from the sibling 'get-page-content' by explicitly noting that it does not return page content, thus clarifying its scope.

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 explicitly tells when to use this tool (to get metadata) and when not to use it (for content, use get-page-content). However, it does not contrast with other siblings like 'get-page-preview' or 'list-pages', which could provide additional guidance. The explicit alternative reference is strong.

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