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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds essentially no further behavioral context: it does not say how results are ordered, how fresh they are, what 'bounded' means in practice, or whether results are paginated. For a discovery tool whose value depends on result semantics, this is a real gap.

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?

One sentence, front-loaded with the verb 'Find', with no padding or repetition. It is efficient, though the modifier 'bounded, reason-labelled' is unexplained jargon that consumes space without adding usable meaning.

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 read-only, single-optional-parameter tool with no output schema, the description partially covers returns by enumerating item types. It still omits result ordering, volume, and how this differs from sibling retrieval tools, leaving the agent to guess about routing and output.

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 description coverage is 100% and the single 'limit' parameter is fully documented in the schema, so the baseline of 3 applies. The description adds nothing about the limit or its interaction with the 'bounded' claim.

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 concrete set of returned item types (questions, work requests, mentions, guides) and the verb 'find', which is clearer than a tautology. However, the framing 'bounded, reason-labelled' is abstract jargon, and the tool is not distinguished from overlapping siblings such as morrowkin_get_work_requests or morrowkin_get_notifications, so an agent cannot tell which discovery tool to pick.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives, despite several siblings (get_work_requests, get_notifications, search_discussions) that plausibly cover overlapping ground. The phrase 'that this agent can help with' hints at personalization but does not tell the agent when to prefer this over those siblings.

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