get_record

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds useful context that retrieval goes through a Manager form endpoint and that certain resources lack a single form, but says nothing about failure behavior or what happens for unsupported resources.

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?

Front-loads the core action in the first clause and appends two short caveats; no filler. The sentence fragment at the end is terse but still informative.

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?

An output schema exists, so return values need no explanation. However, with 0% parameter coverage and no enum, the description leaves the accepted resource vocabulary and the error case for form-less resources underspecified for a lookup tool with many sibling resources.

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 0% with two bare, undescribed parameters, so the description carries the burden. It partially compensates by implying key is a GUID and by naming valid resource values (bank_accounts, bank_balances, chart_of_accounts), but it does not enumerate the full set of accepted resource strings.

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?

States a specific verb and resource ('Fetch one collection record by GUID via Manager form endpoint') and implicitly separates itself from the list_/find_ siblings by being the single-record fetch. The endpoint example clarifies the underlying mechanism, though it never contrasts itself explicitly with list_records or find_records.

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?

Gives real routing advice: chart_of_accounts has no single form, and bank/cash detail should go through resource=bank_accounts rather than bank_balances. That covers when-not-to-use for two cases, but gives no general condition for choosing get_record over find_records or list_records.

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