td_find_empty_space

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

No annotations are provided, so the description carries full burden. It explains the tool finds non-overlapping positions and the direction strategy, but does not explicitly state that it does not modify the network or mention any side effects, authentication needs, or rate limits.

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 concise and well-structured: a brief summary sentence, followed by return value clarification, then a clear Args block listing parameters. No unnecessary information.

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 the 5 parameters and no output schema, the description covers all parameters and the return concept. It could be improved by specifying the exact return type (e.g., a dict with nodeX/nodeY) and handling of edge cases like no space found, but overall it is largely complete.

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 0%, meaning the schema properties lack descriptions. The description compensates fully with an Args block that explains each parameter (parent, width, height, direction, padding) including defaults and allowed values for direction (right, below, grid).

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 uses a specific verb 'Find' and resource 'empty position', clearly differentiating from sibling tools like td_create_op which creates the operator. It explicitly states the tool's purpose and outputs.

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 says 'Returns nodeX, nodeY coordinates that can be passed directly to td_create_op', indicating when to use this tool (before creation). It describes direction strategies but does not explicitly state when not to use or alternative tools.

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