polkit_list_actions

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('list and search') but does not mention read-only nature, permission requirements, potential output size, or error behavior. The agent cannot infer safety or side-effects from the description alone.

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?

The description is a single concise sentence with no filler. The action is front-loaded and immediately understandable, with no wasted words.

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?

The tool is simple with one optional parameter and no output schema. The description covers the basic action but does not mention the return format or any special behaviors like pagination or error handling. For a listing tool, this is mostly sufficient but leaves minor gaps that an agent might need to handle.

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 single parameter filter_query is fully documented in the schema with 'Search term.' The description adds no extra meaning beyond the schema, but with 100% schema coverage, the baseline of 3 applies. The parameter is self-explanatory and the description does not need to compensate.

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 clearly states a specific verb ('list and search') and a specific resource ('registered Polkit action definitions'). It is distinct from sibling polkit tools like polkit_check_auth, polkit_generate_policy, polkit_generate_rule, and polkit_pkexec, so an agent can easily differentiate it.

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?

No explicit guidance on when to use this tool versus the other polkit tools. The name and description imply it is for listing actions, but there is no mention of alternatives or conditions, such as 'use this to see available actions before checking authorization with polkit_check_auth.' The usage context is implied rather than stated.

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