workflowy_get_node__WARNING__prefer_glimpse

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

No annotations are provided, so the description carries the full burden. It mentions 'Retrieve' (implying a read operation) but lacks details on permissions, rate limits, error handling, or what 'retrieve' entails (e.g., full node data vs. metadata). The warning adds some context, but behavioral traits are under-specified for a tool with no annotation coverage.

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 extremely concise and front-loaded with a warning, followed by the core purpose. Every sentence earns its place: the warning is critical for usage, and the retrieval statement defines the action. No wasted words.

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?

Given that an output schema exists, the description doesn't need to explain return values. However, with no annotations, 0% schema coverage, and 2 parameters, the description is incomplete—it lacks parameter explanations and behavioral details. The warning and purpose are helpful, but gaps remain for a tool with this complexity.

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 description coverage is 0%, and the description does not explain the parameters at all. It mentions 'by ID' but doesn't clarify what node_id represents or what secret_code is for. With 2 parameters and no schema descriptions, the description fails to add any semantic value beyond the bare schema.

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 specific action ('Retrieve a specific WorkFlowy node') and resource ('by ID'), distinguishing it from siblings like workflowy_glimpse, workflowy_list_nodes, and workflowy_export_node. It explicitly warns to prefer another tool for reading trees, which helps differentiate its purpose.

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 provides explicit guidance on when to use this tool vs. alternatives: it warns to 'Prefer workflowy_glimpse (GLIMPSE) for reading trees,' indicating a clear alternative and context for usage. This helps the agent understand the tool's specific role among siblings.

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