plan_get

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

With no annotations, description discloses read operation, output features, and authentication requirement. Lacks details on rate limits or error behavior but sufficient for basic usage.

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 sentences, highly concise, purpose stated upfront, no filler. Every word adds value.

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?

Despite clear output description, the tool has 6 parameters with no schema descriptions and no output schema. The description fails to explain parameter roles or provide enough context for correct invocation.

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 coverage is 0% and description provides no explanation for any of the 6 parameters (title, page_id, service, sections, max_lines, with_lines). Agent cannot infer how to populate inputs from description alone.

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?

Clear verb 'Fetch' and specific resource 'plan', with detailed output format (addressable markdown, line numbers, TOC, etag). Distinguishes from siblings by mentioning relation to plan_update_range.

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?

Explicitly states to call before plan_update_range and lists required prerequisites (plan_configure + NOTION_TOKEN). No explicit when-not-to-use or alternative sibling tools mentioned.

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