list_remediation_tasks

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds real behavioral context the annotations cannot: the dual-table union (sn_vul_remediation_task plus sn_vul_vulnerability), where the rule engine actually creates records, and that ordering is by descending risk score.

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?

Front-loaded with the core purpose and the dual-table caveat, then the source_table marker, then filtering/ordering. Dense but every clause carries information; the parenthetical sys_class/prefix detail is slightly heavy but justifies itself by disambiguating the table.

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 output schema, the description usefully discloses the source_table field and the risk-score ordering an agent will see in results. It stops short of describing result shape, pagination behavior, or what happens when the query param conflicts with the state filter.

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%, so all six parameters are already documented including the state-code legend. The description only echoes that state and assignment_group are the primary filters and adds no syntax or format detail; baseline 3 applies when the schema does the heavy lifting.

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 ('List USEM Remediation Tasks') and uniquely explains that it spans two backing tables with a source_table marker, which is more than a restatement of the name. It does not name a sibling it is not, so an agent must still infer why list_vulnerable_items or get_remediation_task differ.

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?

'Filter by state or assignment group; ordered by descending risk score' implies the intended usage context of pulling open remediation work, but there is no explicit when-to-use, no exclusion, and no pointer to alternatives such as get_remediation_task for a single record.

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