List PPP Profiles

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context about built-in profiles but does not disclose any additional behavioral traits such as pagination behavior or whether the list includes inactive profiles. The description does not contradict annotations.

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, clear sentence with no redundancies. It is front-loaded with the core action and includes an important detail about built-in profiles. Every word contributes meaning.

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 list tool with 3 parameters and high schema coverage, the description is adequate but minimal. It does not specify the return format (e.g., array of profile objects) or pagination details, though annotations indicate read-only and idempotent behavior. Without an output schema, the description could be more 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?

Schema coverage is 100% (all 3 parameters have descriptions). The description does not add any extra meaning beyond what the schema already provides. For example, it does not explain the purpose of filtering by name or the limit parameter. Baseline 3 is appropriate since the schema carries the full burden.

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 the tool lists PPP profiles, specifically mentioning built-in profiles like 'default' and 'default-encryption'. The verb 'List' with resource 'PPP profiles' is specific, and the tool distinguishes itself from siblings like 'list_pppoe_clients' which lists connections, not profiles.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., 'list_pppoe_clients' for active connections) or any prerequisites. An agent cannot infer appropriate usage context beyond the obvious listing action.

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