Services_getServiceJobs

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the tool runs in the Kuudo deployment rather than locally, which is useful context, but it does not state whether the operation is read-only, what details are returned, how filtering behaves, or what happens if no filter query is supplied. The promised 'filter query' is referenced but never defined.

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 and front-loaded with the deployment caveat, but 'Catalog entry' is a vague phrase that adds little value. The three sentences are compact, but one sentence is mostly non-informative meta-commentary.

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 no annotations, no output schema, and no parameters defined, the description is too incomplete. It does not explain the filter query format, supported fields, return payload, or relationship to the closely named Services_getServiceJobByServiceJobId. The deployment note is helpful but does not make the tool safely callable.

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 schema declares zero properties and permits additional properties, while the description refers to a 'specified filter query' without explaining its expected shape, keys, or format. Because there are no schema-defined parameters, the description needed to compensate, but it provides only a vague reference to a filter query.

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 a clear verb and resource: 'Gets service job details for the specified filter query.' This distinguishes it from Services_getServiceJobByServiceJobId, which retrieves by a single job ID. The 'Catalog entry' and deployment phrasing slightly muddy the statement, but the core purpose is identifiable.

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 explicit guidance on when to use this tool versus alternatives such as Services_getServiceJobByServiceJobId. It mentions that the tool 'runs in your Kuudo deployment, not here,' which is a useful contextual constraint, but it does not explain when a filter-query lookup is appropriate or how it differs from other service-job tools.

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