list_apps

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

With no annotations provided, the description carries the transparency burden. The verb 'List' implies a read-only operation, and it adds useful behavior about the default app fallback. It does not explicitly state whether any side effects exist, but for a zero-parameter list command, the implied read-only nature is adequate.

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?

Three short sentences, each adding distinct value: purpose, usage timing, and parameter context. The key information is front-loaded, with no filler or repetition.

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 simple listing tool with zero parameters and an output schema, the description fully covers what the tool does and when to use it. It also integrates well with the sibling tools by explaining the optional `app` argument pattern, making the description complete in context.

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 has zero parameters, so there is nothing about this tool's schema to clarify. The description adds valuable context about the default app and the `app` argument on sibling tools, which helps the agent understand the ecosystem, but that is not directly about this tool's parameters. Baseline for a zero-param tool is 4.

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 uses a specific verb 'List' with an explicit resource ('registered mPulse apps and the default app'), making the tool's purpose immediately clear. It is inherently distinct from sibling analytic tools like get_summary or get_metrics, as it returns app identifiers rather than metrics.

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?

It explicitly instructs to 'use this before other tools' so that real app names can be referenced. It also clarifies the behavior of the `app` argument across other tools, which is important context for when this listing tool should be called.

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