analyst_summary_history

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

With no annotations, the description carries the full disclosure burden, and it does so thoroughly: pagination, Pro-only full commentary, no auth required, 60 req/min rate limit, and a list of returned fields. This gives an agent accurate expectations about behavior and restrictions.

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 information-dense and front-loaded with the core action, followed by query modes, limits, restrictions, and field details. The opening phrase is slightly redundant with "Returns a paginated history...", but the overall structure remains 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 output schema and no annotations, the description covers query usage, limits, authentication, rate limiting, the Pro restriction, and all returned fields. An agent has enough context to invoke the tool correctly and interpret its response.

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 input schema is empty, but the description documents the meaningful query parameters: date with YYYY-MM-DD format, analystId with a concrete example, days, and the 90-day maximum. Since the schema provides zero parameter information, this fully compensates and adds clear semantics.

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?

States a specific verb and resource: "Get historical daily AI analyst summaries" with two explicit query modes. It also names the sibling alternative analyst_daily_summary for today's data, making the distinction clear.

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 explicit when-to-use guidance: query by date or by analyst+days, with a 90-day cap and a direct pointer to analyst_daily_summary for today's data. This gives an agent concrete conditions for selecting this tool over a sibling.

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