Run Read-Only Jobber GraphQL

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

No annotations exist, so the description bears full burden. It discloses the read-only nature and mutation blocking, which is key behavior, but omits details like error handling, authentication, or query complexity.

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 exceptionally concise—one sentence with no extraneous words—while still conveying the essential purpose and constraint.

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 complexity of GraphQL queries and lack of output schema, the description falis to cover important context like return format, max query size, or how to use variables, leaving significant gaps for agent 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?

Schema description coverage is 0%, yet the description adds no information about parameters (query, variables); it does not clarify expected format, usage, or constraints beyond what the schema implicitly shows.

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 clearly states it runs a read-only Jobber GraphQL query, using specific verb 'Run' and resource 'Jobber GraphQL query', distinguishing it from sibling tools like jobber_account or jobber_auth_url.

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 mentions mutations are blocked by default, providing a basic usage hint, but lacks explicit when-to-use or when-not-to-use guidance relative to alternatives; it's adequate for a straightforward tool.

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