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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds a meaningful non-obvious guarantee in 'It runs nothing', i.e. listing definitions has no execution side effects. It does not cover pagination or result size, which keeps it below 5.

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?

Three short sentences, front-loaded with what is listed and scoped by job type, followed by the disambiguating 'runs nothing'. Mild redundancy between 'Lists the job definitions' and 'Use it to list job definitions', but nothing is wasteful.

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 simple two-optional-parameter read tool with no output schema, the description covers scope, job-type breadth, return hint ('with their job type') and the no-execution guarantee. Only pagination/volume expectations are absent, a minor gap.

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 100% and both parameters (connection, application) are documented with defaults and a pointer to list_connections. The description only echoes the 'of an application' scoping and adds no format or defaulting detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource (lists job definitions) and enumerates the scope of job types covered (export/import, rules, cube refresh). The clause 'It runs nothing' cleanly separates it from execution-oriented siblings such as run_business_rule or epm_rest_run_job, though no sibling is named explicitly.

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?

'Use it to list job definitions for reference. It runs nothing.' gives an implied usage context and implicitly excludes execution, but it never names an alternative tool (e.g. list_recent_jobs, get_job_details, check_job_status) or states when NOT to use it.

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