indicator_info

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

Discloses that it returns None for unknown indicators and describes the return structure in detail. Since no annotations are provided, this is important behavioral info. No mention of side effects, but it is an indepotent query.

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 concise with a clear main sentence. It includes a list of keys but the mention of runtime column names is somewhat tangential but not detrimental.

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 simple query tool with one parameter, the description covers the essential behavior and return format. The output schema exists and the description aligns, making it complete enough.

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 parameter 'name' is described only implicitly as 'for one indicator'. The schema provides no description, and the tool description adds minimal semantic context beyond being an identifier.

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 it returns structured info for a single indicator, or None if unknown, and lists the keys of the returned structure. However, it does not explicitly differentiate from sibling tools like 'list_indicators' or 'indicator_params', though the function is distinct.

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 on when to use this tool versus alternatives. The description does not provide context about prerequisites or appropriate use cases.

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