get_td_nodes

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

With no annotations, the description must disclose behavioral traits. 'List' implies a read operation, but it does not explicitly state read-only, performance implications, or potential side effects. The mention of detailLevel and limit provides some control but lacks completeness.

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?

Single sentence with clear action and key parameters. No wasted words; front-loaded with purpose and optimization hint. Conciseness is excellent.

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?

Despite 6 parameters and no output schema, the description ignores pattern, includeProperties, and responseFormat. It highlights only detailLevel and limit, leaving agents unaware of other critical options. Lacks completeness for effective tool use.

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 baseline is 3. The description adds 'token-optimized output' which gives context to detailLevel and limit parameters but does not cover other parameters like pattern or includeProperties. It provides marginal additional meaning.

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 lists nodes under a path, which is a specific verb and resource. It distinguishes from sibling tools like get_td_node_errors or create_td_node by focusing on listing. The mention of 'token-optimized output' adds context but does not explicitly differentiate from all alternatives.

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 on when to use this tool versus alternatives like get_td_node_parameters or get_td_node_errors. The description hints at a use case (token optimization) but does not explicitly state when to choose this tool over others.

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