get_user_info

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

Annotations declare readOnlyHint=true. Description adds valuable behavioral context beyond safety profile by specifying exactly what profile attributes are returned (tariff, qualified investor status), helping agent understand data scope without output schema.

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 front-loaded sentence with parenthetical precision. Zero redundancy. Every word earns its place: action verb, resource, domain, and specific field enumeration.

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 0-param read-only endpoint, description adequately covers purpose and return data scope (tariff, qual status). Lacks explicit mention of authentication requirement or response structure, but sufficient given tool simplicity.

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?

Zero parameters per input schema, triggering baseline score of 4. No parameter description needed or expected.

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?

Specific verb 'Получить' (Get) with clear resource 'информацию о профиле пользователя' (user profile information). Specifies domain (T-Investments) and distinguishes from trading-oriented siblings like get_orders or get_portfolio by focusing on user metadata (tariff, qualified investor status).

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?

No explicit when-to-use or alternative comparison (e.g., vs get_accounts), but parenthetical specification of returned fields (tariff, qual status) provides implied usage context for when agent needs user configuration data.

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