Enable a job

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

No annotations provided. Description only states the effect (runs on schedule) but does not disclose permissions needed, reversibility, or any side effects (e.g., immediate trigger). Minimal behavioral context.

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?

Single sentence with no redundant words. Efficiently conveys the tool's action and result.

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 state-change tool with no output schema, the description is adequate but lacks mention of expected return (e.g., success/failure) or preconditions (e.g., job must be disabled). Could be more complete.

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?

Input schema is 100% described with jobId documented as 'Job ID (GUID) from list_jobs'. Description adds no further parameter meaning beyond the schema, meeting baseline.

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?

Clearly states the action (enable) and object (disabled job), with specific outcome (runs on schedule). Distinguishes from sibling tools like disable_job, start_job, stop_job.

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?

Implies use for disabled jobs but does not explicitly state when to use versus alternatives (e.g., start_job for immediate run, or update_job for modifications). No when-not-to-use or prerequisite conditions.

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