Tez Expert Guidance

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

With no annotations available, the description carries the full burden of explaining behavior. It states the tool returns curated knowledge but does not disclose side effects, safety properties, or operational details such as rate limits, error handling, or whether the tool is read-only. Minimal transparency is provided.

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 and well-structured. It consists of two clear sentences: the first states the tool's purpose, and the second lists the available topics. There is no redundant information or fluff.

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?

The description provides the tool's purpose and the valid input values, which are essential for basic usage. However, it lacks information about expected output, return format, or how this tool fits into workflows compared to other tools. More context would be needed for a fully informed agent.

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 already describes the 'topic' parameter with examples. The tool description adds value by enumerating the full set of accepted topics, which is not present in the schema. This clarifies the parameter's range and reduces ambiguity.

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 that the tool provides curated expert knowledge about Tezos topics, using a specific verb ('get') and resource ('expert knowledge about Tezos topics'). It implicitly differentiates from sibling search tools by emphasizing 'curated expert knowledge', but does not explicitly name any alternative or contrast them.

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 offers no guidance on when to use this tool versus the sibling search or grep tools. It only lists available topics and does not indicate scenarios where this tool is preferred or where others should be used instead.

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