Get SQL Agent Scheduled Jobs

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the Azure SQL Database availability caveat and enumerates the returned fields, which is useful behavioral context beyond the annotations, though volume/pagination behavior is unstated.

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?

Two short sentences with no filler; the returned-field inventory is front-loaded and the platform caveat is tucked at the end where it belongs. Every clause carries information.

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?

With no input schema properties, no output schema, and rich annotations, the description covers what an agent needs by naming the returned fields and the platform limitation. It stops short of noting result volume or any ordering, which is minor for a parameterless inventory call.

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 tool takes no parameters, so there is nothing for the description to disambiguate; baseline for a zero-parameter tool applies. The field list instead documents output content, which is a reasonable substitute.

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 the resource (SQL Agent jobs) and enumerates what is returned (schedule, frequency, interval, last run status), so the agent knows this is a full inventory rather than a filtered subset. It is distinguishable from the closely-named sibling mssql_agent_failed_jobs by scope, though it never names that sibling 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?

The description gives a platform exclusion (not available on Azure SQL Database), which is genuine when-to-use guidance, but offers no guidance on when to pick this over mssql_agent_failed_jobs or mssql_agent_alerts. Usage is implied by the name and field list rather than stated.

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