it_ops_github_repository_search

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

The description adds useful auth/routing context: it routes through the platform's domain-agent dispatcher under JWT, tenant, and company scope. Annotations already flag openWorldHint and destructiveHint, so the description does not need to restate them; however, it does not explain what side effects the underlying action may have or how the destructive hint applies to a 'search' 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 compact, uses clear section labels for Args, and front-loads the action and routing context before parameter details. The opening sentence is somewhat redundant with the tool name, but it adds the 'domain agent action' categorization, so it earns its place.

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?

For a tool with an output schema and annotations, the description need not cover return values, but it still lacks what the action does, when to use it, and how to populate inputs. The generic dispatcher-wrapper text leaves critical invocation details unresolved.

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%, so the description must carry parameter meaning. It provides only generic definitions: 'message: Free-text objective' and 'inputs: Optional JSON string of structured inputs.' This distinguishes the two parameters at a high level but omits any tool-specific guidance about what structured inputs are valid or how message/inputs interact.

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 only says 'Run the it_ops domain agent action github_repository_search,' which essentially restates the tool name and adds no behavioral definition. It never explains that the action searches GitHub repositories or what kind of results it returns. The only extra content is routing/dispatcher mechanics, not purpose.

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?

There is no guidance on when to choose this wrapper over the many github_* and it_ops_* sibling tools, nor any mention of alternatives. The routing/scope sentence implies a platform-context requirement but does not say when the domain-agent action is appropriate. Agents are left to infer usage from the name.

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