tdx-account-search

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

No annotations are provided, so the description carries full burden. It mentions 'Search' but doesn't disclose behavioral traits like whether this is a read-only operation, potential rate limits, authentication needs, or what happens on no matches. The description is too vague to inform the agent adequately about how the tool behaves beyond its basic function.

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 with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly without unnecessary details.

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 no annotations and no output schema, the description is incomplete for a search tool with 3 parameters. It lacks details on return values, error handling, or behavioral context, which are crucial for an agent to use it effectively. The high schema coverage helps but doesn't compensate for missing operational insights.

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 already documents all parameters (searchText, isActive, maxResults) with clear descriptions. The description adds no additional meaning beyond what the schema provides, such as examples or usage tips, but this meets the baseline for high schema coverage.

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 states the verb ('Search') and resource ('TDX accounts/departments'), which clarifies the basic purpose. However, it doesn't differentiate this tool from sibling tools like 'tdx-account-get', 'tdx-group-search', or 'tdx-people-search', leaving ambiguity about what specific accounts/departments are targeted versus other search tools.

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 is provided on when to use this tool versus alternatives. With multiple sibling search tools (e.g., tdx-asset-search, tdx-cmdb-search, tdx-group-search, tdx-people-search, tdx-project-search, tdx-ticket-search), the description lacks context about scope, prerequisites, or exclusions, offering minimal help for selection.

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