github_submit_review

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

No annotations are provided, and the description does not disclose any behavioral traits such as whether it is a write operation, authentication requirements, rate limits, or side effects. It merely mentions routing. This is insufficient for an agent to understand the tool's impact.

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 short but not front-loaded with the primary purpose. It wastes space on routing details that are likely implicit. Every sentence does not earn its place; the purpose is buried.

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's complexity and the presence of many sibling GitHub tools, the description is insufficient. It does not explain the review submission process, required arguments structure, or return value (though output schema exists, the description adds no context). An agent would struggle to use this tool correctly.

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 input schema has a single parameter 'arguments' with no description, only a title and type. The tool description adds no meaning beyond what the schema already provides—'JSON string of arguments for the connector operation' is essentially a restatement. With 0% schema description 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 states it is a GitHub connector operation for submit_review, but does not explicitly state that it submits a review on a pull request. The verb 'submit_review' hints at the purpose, but it is vague and not clearly differentiated from sibling tools like github_dismiss_review or github_request_reviewers.

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 on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., existing pull request, review state), context, or exclusions. The description lacks any usage directions.

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