diaspora_community_guide

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

No annotations are provided, so the description carries full responsibility. It only states 'by country' but does not disclose what happens with invalid countries, whether authentication is needed, rate limits, or if the response is paginated. The output schema exists but is not described, so behavior is opaque.

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 very short (one sentence + 'DEMO'), which is concise but at the expense of necessary detail. 'DEMO' is unclear and may mislead. The structure is minimal, but it is front-loaded with the key purpose.

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 the tool has one optional parameter and an output schema, the description should explain what the output contains (e.g., list of organisations, details). It does not. The complexity is low, but the description omits essential context like the scope of resources or output format, leaving the agent underinformed.

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 0% schema coverage for the single parameter 'country', the description adds minimal semantic value by stating 'by country'. It does not explain the default value 'USA', possible values (no enum), or the effect of omitting the parameter. The description barely compensates for the missing schema documentation.

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 provides 'Kenya diaspora community resources and organisations by country', which distinguishes it from sibling tools like diaspora_tax_guide or diaspora_verification. The verb 'guide' implies a listing or directory. However, the inclusion of 'DEMO' adds ambiguity about whether the tool is functional or a placeholder.

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 versus siblings. It is implicit that it is for finding community resources, but no explicit alternatives or prerequisites are mentioned. The description does not clarify when one would choose this over, say, diaspora_tax_guide for tax information.

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