search-community

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

No annotations are provided, so the description carries the full disclosure burden. It states the return shape ('results with id for get-community-post') and an actionable post-call constraint ('Include at least one community insight in your answer'), but says nothing about result limits, pagination, or auth/scope requirements.

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?

Front-loaded with the core purpose, then organized under scannable headers (PRIMARY use cases / MUST use when / After calling / Returns). Every bullet carries routing or workflow information; nothing is padding.

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 single-parameter search tool with no output schema, the description covers purpose, triggers, and what the results contain, and even specifies the next tool to call. Nothing an agent needs to invoke or sequence it correctly is missing.

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?

Schema coverage is 100% for the single 'query' parameter, so the schema already documents its type and purpose. The description adds example queries ('authentication', 'react-native'), but those duplicate the schema example, so this is the baseline 3.

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?

States a specific verb and resource: 'Search real-world FeathersJS solutions from the community.' It also implicitly scopes itself against siblings like search-doc and get-doc by targeting solutions 'not in docs,' so the agent can distinguish it without opening a schema.

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?

Explicit 'PRIMARY use cases' and a directive 'You MUST use this when' list three concrete triggering conditions, including negative-style guidance ('solution is not clearly in a single doc page') that routes the agent away from doc search. It also names get-community-post as the follow-up alternative.

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