mcp-agno

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

No annotations provided, so description carries full burden. Mentions URLs are returned, which adds behavioral context beyond the tool name. However, lacks details on pagination, rate limits, or whether results are cached/static.

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?

Single sentence with zero waste. Front-loaded with action verb. Appropriate length for a parameter-less list operation.

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?

Appropriate for tool complexity (zero inputs, simple listing). Note that output schema exists, so detailed return value explanation is not required in description. Mentioning URLs provides sufficient context for what the tool provides.

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?

Zero parameters present, which per guidelines sets a baseline of 4. Description does not need to compensate for parameter documentation gaps.

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?

Clear verb 'List' and resource 'AGNO documentation sections', with specific detail that URLs are returned. Lacks explicit differentiation from sibling tools get_agno_page (retrieve specific content) and search_agno_docs (search), though the described action differs implicitly.

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 provided on when to use this discovery/index tool versus retrieving specific pages (get_agno_page) or searching (search_agno_docs). No prerequisites or workflow context mentioned.

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