segnals_get_pnl_summary

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

No annotations are provided; the description adds a scope requirement ('Requires scope: read:stats') and an example call. This is adequate for a simple read operation, but it lacks details on data freshness, return format, or any potential 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?

Two sentences plus an example line with no wasted words. The purpose is front-loaded, and the structure is efficient.

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?

Despite having no parameters and no output schema, the description could be more explicit about what the 'breakdown' includes (e.g., time periods, granularity). While adequate for a simple tool, it leaves some ambiguity about the return value.

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 schema coverage is 100%. The description does not need to explain parameters, and none are present. Baseline for 0 parameters is 4, which is appropriate here.

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 verb 'Get' and the resource 'aggregated PnL (profit and loss) breakdown from the dashboard data', with specific purpose 'analyze profitability over time'. It is distinct from sibling tools which focus on other aspects like bots, listings, or account info.

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 a clear usage context ('analyze profitability over time') and includes a scope requirement. However, it does not explicitly mention when not to use this tool or compare with alternatives, though the sibling set is diverse and no direct alternative exists.

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