find_nodes

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

Discloses full-scan indexing with no query, case-insensitive substring matching across multiple fields, status filter, sheet scoping, and boardRef leaf behavior. All behavioral traits are covered despite no annotations.

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?

Somewhat verbose but every sentence adds value; front-loaded with main purpose. Minor room for tightening without losing clarity.

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 zero annotations, no output schema, and three optional params, the description thoroughly covers functionality, edge cases (boardRef), and result usage, making it fully self-sufficient.

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?

All three parameters (query, sheet, status) are explained in detail: query is case-insensitive substring against specific fields, status is a filter with values, sheet scopes to one sheet. Adds meaning beyond the empty 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?

Clearly states it finds workflow nodes by text or status and returns paths, distinct from siblings like get_node (read) and set_node (patch).

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 advises when to use (jump to a card), how to use results with get_node/set_node, and provides special handling for edit_board by dropping last path id.

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