td_list_ops

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

No annotations provided, so the description must disclose behavioral traits. It does not state whether the operation is read-only, what side effects exist, or any authorization needs. It only describes parameters and core action.

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 as a docstring with an Args section. Every sentence serves a purpose, with no unnecessary words. A slight dock for not being front-loaded with the key action.

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 covers the core purpose, filtering, and pagination. However, given 6 parameters and no output schema, it lacks details on return format, error handling, or the meaning of 'child' hierarchy. Adequate but not thorough.

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%, but the description adds meaningful explanations for each parameter (e.g., 'Parent path to list children of', 'Filter by family'). This adds value beyond the schema's titles. However, it does not provide examples or detailed formats.

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 it lists child operators with filtering and pagination. It uses a specific verb ('list') and resource ('child operators'), and distinguishes from siblings like td_get_op_info (single op info) and td_create_op (creation).

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 usage for listing ops with filtering, but does not explicitly state when to use this tool vs alternatives (e.g., when to use td_get_root or td_find_empty_space). No exclusions or prerequisites are mentioned.

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