Get TacticalRMM Agent

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

The description says 'This tool is read-only', which directly duplicates the readOnlyHint annotation. It adds no new behavioral context beyond repeating the annotation and the endpoint path. No information about error handling, return format, or side effects is provided, though annotations already cover the read-only and idempotent nature.

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 concise, consisting of two short sentences. The first sentence is front-loaded and informative. However, the second sentence ('This tool is read-only.') is redundant with the annotation, so it does not fully '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?

For a simple get-by-id operation, the description is adequate. It specifies the required agent_id and the read-only nature. Although there is no output schema and the description does not detail the response structure, the schema's response_format parameter and the straightforward nature of a single-record fetch make this sufficient.

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 provides descriptions for both parameters (agent_id and response_format) with 100% coverage. The description adds no additional meaning beyond what is in the schema, so the baseline score of 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?

The description clearly states 'Get one TacticalRMM agent record by agent_id', specifying the exact resource and how it is identified. It distinguishes from sibling tacticalrmm_list_agents by using 'one' versus implying a list operation. The endpoint '/agents/<agent_id>/' adds further specificity.

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 tool is used when you have a specific agent_id and need that single record, but it does not explicitly mention when not to use it or suggest alternatives for listing all agents. The usage context is clear but not fully elaborated.

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