get_legend_context

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

Discloses output content and includes a disclaimer, but does not mention operational traits like authentication needs, rate limits, or side effects. With no annotations, the description should cover more behavioral aspects.

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?

Well-structured with bullet points and sections, front-loaded with purpose. Slightly verbose but each section adds information; could be more concise.

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?

Covers the output details, formats, and use cases adequately without an output schema. Minor gaps in parameter behavior documentation (e.g., effect of include_related).

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 coverage is 100%, but the description adds value by explaining the output for each format and the use cases, expanding beyond schema descriptions.

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 this tool retrieves detailed information about legendary founders/investors, listing specific content categories. However, it does not explicitly distinguish itself from sibling tools like get_legend_insight or list_legends.

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 some context on when to use (e.g., 'When to consult this legend') and available formats, but lacks explicit guidance on when not to use it or how it compares to alternatives.

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