Get account

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

Description clearly indicates read-only behavior and specifies returned fields. Though no annotations exist, the description adequately discloses the operation's nature without contradictions.

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?

Single sentence with no unnecessary words. Information is front-loaded and every part is valuable.

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 operation with no output schema, the description lists the returned fields sufficiently. Could be slightly more detailed about the 'descriptors' field, but overall 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?

No parameters in schema, so description adds no param info, but baseline for 0 params is 4. The schema is fully documented by its emptiness.

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?

Clearly states the tool gets the authenticated Datto RMM account details and lists specific fields (name, UID, currency, descriptors). Distinguishes from sibling get tools which target other resources.

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?

While no explicit when/when-not guidance is given, the tool is self-explanatory for its simple read-only purpose, and no alternative tool exists for getting account details. The context is clear.

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