Jobs-tools-knowledgeBase-deletePage

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Delete a page,' implying a destructive operation but omitting whether deletion is permanent, cascades to children, requires special permissions, or can be undone. This is a significant gap for a delete tool.

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 a single, concise sentence with no wasted words. It is efficiently front-loaded, though it lacks structural elements that could provide additional context. For a simple tool, this level of conciseness is acceptable.

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 destructive tool with no annotations and no output schema, the description is insufficient. It doesn't explain return values, error behavior, side effects on related data, or what constitutes a successful deletion. The two parameters are documented, but the overall operational context is missing.

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?

Both parameters are fully described in the schema ('Page ID' and 'Project ID'), so the baseline is 3. The description adds no additional meaning, such as the relationship between projectId and pageId or any constraints, but the schema already covers the basics.

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 deletes a page, using a specific verb and resource. It distinguishes from siblings like getPage and upsertPage, but doesn't clarify whether 'page' includes guide notes or other entity types, so it's not fully differentiated.

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?

No guidance is provided on when to use this tool versus alternatives like archiveNote or deleteProject. It lacks prerequisites, exclusions, and example scenarios, leaving the agent without contextual decision support.

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