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

Annotations already provide readOnly/openWorld/destructive hints; the description adds useful behavior beyond them: the tool is curated-only, public-safe, and expressly does no live memory/repo/vault reads, and it discloses the 4 MESH/call cost. No contradiction with the annotations.

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 core behavior, exclusions, and cost are packed into one front-loaded sentence, and the parenthetical is efficient. It is slightly cryptic ('tool · knowledge', '4 MESH/call'), but nothing is padded.

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 one-parameter tool with a nested payload and no output schema, this description would need to specify the request shape and return format to be safely callable. It provides purpose and scope but leaves the core 'what do I put in input and what comes back' undefined, and the schema description directs the agent to unrelated tool payloads.

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's only parameter is a generic 'input' object with examples for agent-brain and agent-memory, neither of which is this tool. The main description does not clarify the expected payload for DevDesk COG Public Ask, so the nominal 100% coverage does not actually help an agent formulate the correct question/query object.

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 names a specific operation (Public-safe Q&A) over a defined resource (audited DevDesk COG facts) and lists the topics covered. The 'Curated only; no live memory, repo, or vault reads' clause distinguishes it from memory/repo tools among the siblings, though it does not explicitly name a sibling to prefer.

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 implies when it is appropriate: ask about audited COG facts, curated information, public-safe questions. It gives an exclusion ('no live memory, repo, or vault reads') but never states when to use an alternative tool or names alternatives, so the agent is left to infer routing from context.

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