workflowy_report_created

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

Annotation destructiveHint=true contradicts the description of a read-only ranking operation. The description does not disclose destructive behavior or other side effects. Annotation contradiction present.

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 concise sentence, but it could benefit from slightly more detail without becoming verbose.

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?

The description is too brief given the tool's 4 parameters and lack of output schema. It does not explain return format, the meaning of parameters in context, or address the contradiction with annotations.

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 100%, so the schema already documents parameters. The description adds no additional meaning beyond what parameters are, missing details on how 'method' or 'preserve_tags' affect the ranking.

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 action (rank nodes) and the ordering (by creation date, oldest first). It distinguishes from sibling tools like workflowy_report_modified which ranks by modification date.

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 wanting oldest nodes first, but provides no explicit guidance on when not to use or how it compares to siblings like workflowy_report_modified or workflowy_report_children.

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