slide_get_agent_services

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

No annotations are provided, so the description carries the full burden. It clearly indicates a read-only list operation ('Get') and scopes the result to 'backed-up services ... detected on an agent.' It does not mention authentication or edge cases, but for a simple list tool this is adequate transparency.

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 one front-loaded sentence with no filler. The parenthetical examples are valuable because they disambiguate what counts as a 'service,' making every word earn its place.

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 has only one required parameter and no output schema or annotations, so the description does not need extensive caveats. It conveys both the input (agent_id) and the return subject (list of backed-up services). A minor gap is the lack of explicit return format details, but this is not critical for a simple list operation.

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 schema already documents agent_id as 'Agent ID.' with 100% coverage, so the baseline applies. The description reinforces that agent_id is the agent whose services are listed, but it adds no additional format, validation, or behavioral detail beyond the schema.

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-resource pair: 'Get the list of backed-up services' and clarifies with concrete examples ('installed applications, database engines'). The scope is clearly tied to a single agent, which distinguishes it from sibling tools like slide_get_agent or slide_get_agent_file_versions.

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 implies the intended use: call this when you need the backed-up services detected on a specific agent. However, it does not explicitly state when not to use it or mention any alternative tools, so guidance is implied rather than fully articulated.

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