Get account

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond those annotations, such as how account lookup works or what happens when no identifier matches.

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 short sentence, but its brevity reflects under-specification rather than effective conciseness. It is front-loaded only in the sense that there is nothing else to place after it.

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 3-parameter lookup tool with no output schema, no parameter documentation, and no behavioral detail, the description is completely inadequate. An agent cannot confidently invoke this tool or know what it returns.

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 3 optional identifier parameters (name, number, sys_id) with 0% schema description coverage, and the description adds no meaning for any of them. It does not explain whether these are alternative lookup keys or how they should be used.

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 says only 'Invoke the get_account operation,' which restates the tool name and title rather than explaining what an account is or what retrieving one entails. It does not distinguish this tool from the many sibling lookup tools such as servicenow_get_application or servicenow_get_cmdb.

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?

There is no when-to-use guidance, no mention of prerequisites, and no reference to alternatives. The description gives an agent no basis for choosing this tool over the many other ServiceNow get_* siblings.

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