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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the description's added value is the auth/connection requirement ('asks them to connect'), which is genuinely useful context not in the structured fields. It also names the status lifecycle (draft, applied, discarded, replaced, expired), helping the agent interpret results, though it says nothing about result volume or pagination despite the limit parameter.

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 compact sentences with zero filler, and the access constraint is front-loaded before the payload description. Slight weakness: it opens with an eligibility clause rather than a verb stating the action, so the purpose arrives in the second sentence.

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 with full annotation coverage and no output schema, the description does the important remaining work: access prerequisites and the shape of returned data. The main gap is that ordering and result-size behavior around limit are left unstated.

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 limit parameter has 0% schema description coverage, so the description carries the full burden and does not compensate: it never explains what limit controls, its default of 10, or the max of 20. The only hint is the word 'recent', which loosely implies newest-first ordering, but that is not stated.

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 identifies the resource: the connected creator's recent Page drafts, and even enumerates the returned fields (status values, applied parts, preview link). It does not explicitly name a sibling it differs from (e.g., get_page for a single design, design_page for creating one), but the plural 'drafts' resource makes the distinction inferable.

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?

'Creators only, on their own Piku account' establishes who can call it and the connection prerequisite. There is no explicit statement of when to prefer this over get_page or how it relates to send_draft / design_page, so the usage boundary is only implied.

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