agno_reference

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

With no annotations, the description explains it is a read-only reference tool that returns documentation. It does not specify side effects, but that is appropriate. Provides good behavioral context.

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?

Short, front-loaded description with no wasted words. Uses a clear structure: purpose, args, and differentiation.

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 one parameter and no annotations, the description covers purpose, parameter semantics, and usage context completely. Output schema exists but is not needed for completeness.

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?

Despite 0% schema coverage, the description adds a clear list of allowed topics and explains that the topic selects the SDK class documentation. This compensates well.

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 gets Agno SDK class and method reference, with specific examples of what it returns (Agent() constructor parameters, etc.). It distinguishes from sibling agno_agentos by noting the latter is for runtime REST API endpoints.

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?

Explicitly mentions when to use this tool for SDK docs and when to use agno_agentos for runtime API endpoints. Also lists allowed values for the topic parameter.

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