boj_github_graphql

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

No annotations are provided, so the description carries the full burden. It states 'Execute a GitHub GraphQL query,' which implies a write operation could be possible (e.g., mutations), but doesn't clarify authentication needs, rate limits, error handling, or what 'execute' entails (e.g., returns raw GraphQL response). This leaves significant behavioral gaps for an agent.

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 no wasted words. It's front-loaded and gets straight to the point, making it easy to parse quickly.

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, 0% schema coverage, no output schema, and 2 parameters (one nested), the description is incomplete. It doesn't cover authentication, error cases, return format, or how to structure queries/variables, leaving the agent with insufficient context for reliable use.

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 0%, so the description must compensate. It mentions 'GitHub GraphQL query,' which hints at the 'query' parameter's purpose, but doesn't explain the 'variables' parameter or provide any syntax examples, required scopes, or format details. This adds minimal value beyond the bare schema.

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 'Execute a GitHub GraphQL query' clearly states the action (execute) and target (GitHub GraphQL query), which is better than a tautology. However, it's somewhat vague about what specifically is executed (e.g., raw queries vs. predefined operations) and doesn't distinguish it from sibling tools like boj_github_get_repo or boj_github_list_issues, which might also use GraphQL internally.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling GitHub tools (e.g., boj_github_get_file, boj_github_list_issues), it's unclear whether this is for custom queries when those specific tools are insufficient, or if it's the primary interface. No exclusions or prerequisites are mentioned.

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