get_process_definition

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

With no annotations, the description carries full burden. It only implies a read operation via 'Get' but does not disclose behavioral traits like idempotency, side effects, authentication needs, or rate limits. The lack of details on return behavior (e.g., pagination, ordering) is a gap.

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 extremely concise: two sentences for purpose and parameters, plus Returns line. Front-loaded with purpose, every sentence earns its place without redundancy or fluff.

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 output schema, the description only vaguely states 'returns process definitions with their configuration.' For a simple tool with two optional params, this is adequate but lacks specifics on the structure of the response. It could mention whether results are a list or single object.

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 coverage is 0% (no description in schema), so the description adds value by explaining process_name as 'optional specific process name' and process_type as 'optional filter by type' with an example. This clarifies parameter semantics beyond the schema's titles.

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 retrieves 'process scheduler definitions' and specifies optional filters (process_name, process_type). The verb 'get' and resource are clear, and the tool distinguishes itself from siblings that target different entities (e.g., steps, results), though no explicit differentiation is provided.

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 over alternatives. The description only lists parameters without context about prerequisites, common use cases, or when not to use it. Sibling tools like get_application_engine_steps are not referenced.

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