it_ops_github_repository_search

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only notes routing through a domain-agent dispatcher and scoping under JWT/tenant/company, but fails to describe what the tool does, side effects, or return value. This is insufficient for safe invocation.

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 very short (3 lines) with no extraneous text. However, the brevity results from lacking content rather than efficient communication. It earns a baseline score for being non-redundant but not more.

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 tool has no annotations and sparse parameter descriptions, the description leaves critical gaps: the agent cannot determine what the tool searches for, what inputs are valid, or what output to expect. Completeness is inadequate for a tool amid many siblings.

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?

The description adds minimal meaning beyond the parameter names: 'Free-text objective' and 'Optional JSON string' are generic and do not explain expected formats, allowed keys, or example values. With 0% schema coverage, the description fails to compensate.

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 restates the tool name ('Run the it_ops domain agent action github_repository_search') without specifying what the action actually does. It mentions routing scope but not the actual search purpose, leaving the agent to guess how 'github_repository_search' differs from other 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 like specific GitHub API tools or other domain agent actions. The description does not clarify what type of search to perform or when to supply structured inputs.

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