github_list_workflow_jobs

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

No annotations provided; description lacks behavioral traits like read-only, destructive, or idempotent. Generic routing info does not disclose safety or side effects.

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?

Short description but includes unnecessary routing detail ('Routes through /api/tools/invoke...') that is not actionable for tool selection or invocation. Could be more concise.

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?

Despite having an output schema, the description does not mention what the tool returns or link to the output schema. Incomplete for a list operation; agent cannot infer expected output or usage.

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?

Single parameter 'arguments' described as 'JSON string of arguments for the connector operation' – insufficient beyond schema. With 0% schema description coverage, expected keys or examples are missing, leaving the agent guessing.

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?

Description tautologically restates tool name as 'Github connector operation list_workflow_jobs' without explaining what workflow jobs are or why an agent would use this tool. No distinction from siblings like github_list_workflow_runs.

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 vs alternatives. With many sibling GitHub tools, lacking context on appropriate scenarios (e.g., listing jobs for a specific workflow run).

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