Discover Fediverse Instances

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

Description adds that it uses the instances.social API and is real-time, but annotations already indicate readOnlyHint=true. No additional behavioral details like rate limits or caching behavior are 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?

Single sentence, front-loaded with verb and resource. Efficiently conveys purpose, though could benefit from slight elaboration on filtering capability.

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?

No output schema, yet description does not explain return format or result structure. For a tool with 8 parameters and no output schema, description should provide more context about what the discovery returns.

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?

With 100% schema description coverage, baseline is 3. Description mentions 'advanced filtering' but does not add specific parameter meaning beyond what the schema already provides.

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?

Description clearly states verb ('Discover') and resource ('fediverse instances'), and adds real-time aspect and API source, distinguishing it from sibling tools like 'get-instance-info' which retrieves a single instance.

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 vs siblings like 'get-instance-info' or 'search'. Only describes functionality without usage context or exclusions.

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