get_sample_portfolio_data

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

With no annotations provided, the description carries full burden. It states the tool returns sample data (read operation) with realistic parameters, implying no side effects or destructive actions. It does not elaborate on data limits or mutability, but the simplicity of the tool makes this adequate.

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: two sentences plus a bullet point. The main purpose is stated in the first sentence ('get pre-defined sample portfolio data for quick testing'), making it front-loaded. No unnecessary words.

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?

Given the tool's simplicity (no parameters, clear output schema), the description is complete. It specifies the tool returns sample portfolio data for testing, and ties it to a sibling tool (create_portfolio). The output schema exists and is referenced, so explanation of return values is unnecessary.

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 zero parameters, so the description does not need to add parameter detail. According to the guidelines, for 0 parameters the baseline score is 4. The description adds value by specifying the output is a dictionary ready for create_portfolio().

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 retrieves pre-defined sample portfolio data for testing. It uses a specific verb ('get') and resource ('sample portfolio data'), distinguishing it from sibling tools like create_portfolio which actually create portfolios.

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 indicates usage for 'quick testing' and explicitly mentions the output is 'ready for use with create_portfolio()', providing clear guidance on when to use this tool (testing) and how to chain it with another tool. It does not specify when not to use it, but the context is sufficient.

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