list_services

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

Annotations already cover read-only and non-destructive behavior, so the safety bar is lower. However, the description says nothing about pagination despite the cursor parameter, nor about what 'visible for a profile' means (permissions, filtering, ownership). It adds little behavioral context beyond the verb.

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, front-loaded and free of waste. It is appropriately sized for the amount of information it conveys, though that amount is small.

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 paginated list tool with no output schema, the description omits pagination behavior, what fields are returned, and how 'profile visibility' is scoped. An agent cannot determine how to iterate results or what to expect back.

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 0%, but the three parameters (limit, cursor, username) are self-explanatory by name and type, with limit having bounds/defaults. The description adds nothing about their semantics, so baseline 3 is appropriate.

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 services') with a scope qualifier ('visible for a profile'). It does not differentiate from sibling tools like get_profile or get_status, but among the list-style operations it is clear.

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 guidance on when to use this versus the many sibling read tools (get_status, get_profile, get_context). The agent is left to infer that this specifically enumerates services.

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