get_valuations

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'Get', implying a read operation, but does not mention whether the session must be active, if the call is safe, or any potential side effects or limitations.

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 extremely concise and front-loaded: a single clear purpose statement followed by a minimal parameter list. Every sentence contributes necessary information with no filler.

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 getter with two parameters and an output schema, the description is mostly complete. It covers the tool's purpose and parameter provenance. It could briefly note session freshness or when to prefer this over get_holdings, but the core context is sufficient.

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?

Despite 0% schema coverage, the description adds meaningful parameter context by explaining where to get the values ('from list_sessions', 'from list_accounts'). This goes beyond the bare schema by establishing provenance and relationships to sibling tools.

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 tool 'Get the valuation summary for an account', identifying a specific verb and resource. It differentiates from siblings like get_holdings or get_transactions by focusing on valuation summary, though it does not explicitly call out the distinction.

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?

The description provides clear usage context by specifying that session and account_id are obtained from list_sessions and list_accounts respectively, implying the prerequisite calls. It does not explicitly discuss alternatives or exclusions, but the arg provenance guidance is actionable.

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