get_summary

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

No annotations are provided, so the description carries the burden. It states the tool returns a broad set of fields across multiple views, indicating a comprehensive aggregate response. The word 'Returns' and 'snapshot' imply a read-only operation. It does not disclose authentication or rate limits, but these are less critical for a simple data retrieval tool.

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 two sentences: the first gives a specific purpose, the second adds usage context. Both are informative and free of fluff, making it appropriately compact and front-loaded.

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 single-parameter tool with no output schema, the description provides sufficient context: the full list of data categories, how it relates to other endpoints, and when to use it. The agent can confidently decide to invoke it without needing additional information.

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 schema has one parameter, 'symbol', with a description 'Asset identifier (ticker symbol).' The description mentions 'single asset symbol' but provides no additional format or syntax details. With 100% schema coverage, the baseline of 3 is appropriate.

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 it 'Returns a unified snapshot of identity, profile, market data, fundamentals, ownership, analyst coverage, and fund metrics for a single asset symbol.' This clearly specifies the action, resource, and scope, and differentiates itself as a comprehensive aggregate versus sibling tools like get_profile or get_statistics_general.

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 explicitly says 'Use it when you need fast, accurate, high-coverage data for a ticker without orchestrating multiple endpoints.' This provides clear usage context, though it does not explicitly name alternative tools for exclusion, only implies them.

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