get_public_user_bot_readme

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

With no annotations, the description carries full burden. It discloses the read-only nature and auth requirement, but lacks details on error behavior, rate limits, or response format. Adequate for a simple public read, but basic.

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?

Two concise sentences contain all essential information with no redundancy. Extremely efficient for the information conveyed.

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 public read tool with 2 params and no output schema, the description covers core behavior and auth. However, it omits error scenarios and does not leverage sibling context to differentiate itself more clearly.

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 describes botUsername but not username. The tool description adds no parameter clarification, leaving the relationship between username and botUsername ambiguous. Schema coverage is 50%, and description does not compensate.

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 retrieves 'description and README markdown for a published bot' and notes 'No authentication required,' making it distinct from sibling tools like get_bot_readme (likely auth-required) and get_public_user_bot (full info).

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?

It provides a key usage condition ('No authentication required') but does not explicitly state when to use this tool versus alternatives like get_bot_readme or get_public_user_bot. More explicit guidance would improve selection.

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