profiles_statistics

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get key statistics', implying a read operation, but does not mention any specific behavioral aspects like data freshness, pagination, or any limitations. The one-line description adds minimal value beyond what the tool name suggests.

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, using a single short sentence with no redundant words. It front-loads the action and resource, which is efficient, though the brevity sacrifices specificity. For what it conveys, it is appropriately structured.

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 large set of sibling tools, especially within the profiles_ family, the description is incomplete. It fails to explain what 'key statistics' includes, what distinguishes it from profiles_summary or profiles_info, and there is no output schema. An agent would not know what data to expect from this call.

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?

Schema description coverage is 100% and the only parameter 'ticker' is described as 'Stock ticker'. The description adds no additional meaning beyond the schema, so the baseline score of 3 applies. It neither enriches nor contradicts the parameter definition.

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 states a clear verb ('Get') and resource ('key statistics for a ticker'), but 'key statistics' is vague and does not distinguish it from sibling profile tools like profiles_summary or profiles_info. It is not a tautology, but it fails to specify the exact nature of the statistics, making it difficult for an agent to select this tool over alternatives.

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 guidance is provided on when to use this tool versus sibling tools such as profiles_profile, profiles_summary, or profiles_recommendation. The description gives no context for selection, leaving the agent to infer based on the name alone.

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