List profile functions

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine domain context about what the returned objects represent (duty-shaping rules), but says nothing about completeness, ordering, or whether the list is global — with annotations carrying the safety burden, this is adequate but not rich.

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 short sentence with zero padding and the key concept front-loaded. It is slightly under-specified rather than verbose, which costs it little here.

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 parameterless read-only list with no output schema, the description gives just enough to know the subject matter, but leaves open whether the result spans all profiles or a subset, and gives no hint of volume. It is minimally sufficient but not 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description's domain gloss on the returned entities is a mild bonus.

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 is a noun-phrase definition of what a 'function' is (duty-shaping rules with min/max duty, step sizes, hysteresis) rather than a statement of what the tool does — no verb like 'list' or 'return'. It does helpfully differentiate the resource from profiles/modes, and the title supplies 'List', but on its own it stops short of a clear action statement.

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?

There is no guidance on when to call this versus siblings such as list_profiles or list_devices, nor any precondition or exclusion. The agent must infer from the name alone that this enumerates all function definitions globally (there are no parameters to scope them).

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