get_margin_attributes

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

The description aligns with readOnlyHint=true (uses 'Получить'/Get). It adds valuable domain context by defining what 'margin attributes' specifically includes (liquid portfolio, initial margin) and identifies the external system (T-Investments), but doesn't address error handling, rate limits, or data freshness.

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 dense sentence that front-loads the action. The parenthetical specifics (liquid portfolio, initial margin) efficiently clarify the return value. No wasted words, though slightly information-dense.

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?

Appropriately complete for a simple read-only tool with one parameter. Compensates for missing output schema by defining the semantic content of the return value (liquid portfolio, initial margin). Given the low complexity and presence of annotations, no further elaboration is necessary.

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?

With 100% schema description coverage, the schema fully documents the accountId parameter. The description doesn't add parameter-specific details beyond what's in the schema, which warrants the baseline score of 3 for high-coverage schemas.

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 the action (Получить/Get) and resource (margin attributes), specifying exactly what data is returned (liquid portfolio, initial margin). It distinguishes implicitly from sibling tools like get_portfolio by focusing specifically on margin-specific metrics, though it doesn't explicitly name alternatives.

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?

Provides prerequisite guidance by noting that accountId can be obtained via get_accounts. However, it lacks explicit guidance on when to use this tool versus similar siblings like get_portfolio or get_positions, and doesn't specify when not to use it.

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