get_page

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

Annotations already indicate 'readOnlyHint: true', making the read-only nature clear. The description adds 'Get the full content' which is consistent but provides no additional behavioral context such as error handling, permissions, or what constitutes 'full content'.

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 sentence that is concise, front-loaded, and contains only necessary information. No 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 simple tool with one parameter, no output schema, and a clear read-only annotation, the description is mostly complete. However, it lacks details on what 'full content' includes (e.g., formatting, attachments) and does not explain return format or pagination.

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 covers 100% of parameter descriptions, so the baseline is 3. The tool description does not add any extra meaning beyond the schema's 'The ID of the page to retrieve'.

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 specifies the action ('Get'), the resource ('full content of a specific knowledge base page'), and the platform ('Productive.io'). It effectively distinguishes from sibling tools like 'list_pages' (list vs get) and 'copy_page' (copy vs get).

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 use when retrieving a single page's full content, but does not explicitly state when to use it versus alternatives (e.g., 'list_pages' for summaries, 'copy_page' for duplication). No when-not or prerequisites are provided.

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