tdx-cmdb-search

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

With no annotations provided, the description carries full burden but only states it's a search operation. It doesn't disclose behavioral traits like whether this is read-only (implied but not explicit), rate limits, authentication needs, pagination behavior, or what happens on errors. For a search tool with 7 parameters and no annotations, this is inadequate.

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 a single, efficient sentence that gets straight to the point without unnecessary words. However, it could be more front-loaded with critical context given the lack of annotations and sibling tools.

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 complexity (7 parameters, no output schema, no annotations, and many sibling tools), the description is incomplete. It doesn't explain return values, error handling, or how this differs from other search tools in the server. For a search operation in a crowded toolset, more contextual guidance is needed.

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 100%, so the schema fully documents all 7 parameters. The description adds no additional meaning beyond 'with filters', which is already implied by the parameter names and schema descriptions. This meets the baseline of 3 when schema coverage is high.

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 verb ('Search') and resource ('TDX configuration items'), making the purpose understandable. However, it doesn't differentiate this from sibling tools like 'tdx-cmdb-get' or 'tdx-cmdb-update' beyond mentioning 'search' functionality, which is implied by the name.

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 no guidance on when to use this tool versus alternatives like 'tdx-cmdb-get' (for retrieving specific items) or 'tdx-cmdb-update' (for modifications). It mentions 'with filters' but doesn't explain when filtering is appropriate or what scenarios warrant this search tool over others.

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