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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing behavioral beyond restating the operation, giving no detail on error or missing-job behavior.

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?

A single front-loaded sentence with zero padding, which is structurally sound. However, the brevity reflects underspecification rather than efficient communication, since nothing of value is conveyed beyond the title.

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 read tool with no output schema, the description is thin: it does not say what a 'repurpose job' contains, what a returned job's status might be, or how to interpret the response. Annotations cover the safety questions, but the agent is left to guess at the resource's contents.

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 50%: workspace_id and query are documented in the schema, while id and brand_id are not. The description echoes only 'by id', which is already the required parameter, so it does nothing to compensate for the undocumented brand_id or the semantics of the query override object.

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 gives a specific verb (get) and resource (repurpose job) with an explicit scope ('single ... by id'), so an agent knows it is a point-fetch rather than a list. It never names the sibling it complements, aidelly_list_repurpose_jobs, so differentiation is implicit rather than stated.

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 only guidance is the word 'single' and 'by id', which implies a lookup. There is no statement of when to use this instead of aidelly_list_repurpose_jobs, no prerequisite such as a prior job id, and no note on what happens if the job is absent or still running.

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