Dearovo MCP

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

With no annotations, the description carries the full behavioral burden. It does disclose a useful negative capability — it does not access personal accounts or store relationship information — which signals a safe, non-persistent lookup. However, it says nothing about what a call actually returns, whether it is read-only, or any access 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?

Two short sentences with no filler, and the core action is front-loaded before the privacy caveat. Efficient, though slightly cryptic rather than genuinely informative.

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 tool with an unspecified return shape (no output schema, no annotations), the agent still lacks any sense of what it gets back or how the required occasion parameter shapes results. The privacy note is the only substantive addition.

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 0%, so the description should compensate, and it does not mention either parameter. The enums are self-describing mechanically, but nothing explains what "occasion: other" or the recipient values mean semantically or how they steer the result.

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?

It has a verb ("Find") and a named resource ("Dearovo writing experience"), but "writing experience" is vague about what is actually returned — templates, samples, or guidance. It also never distinguishes itself from the sibling message_writing_tips, so an agent must guess which to call.

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?

The description gives no when-to-use guidance and never mentions the alternative message_writing_tips or any condition that selects one over the other. The only implied context is "a message you want to send," which is minimal.

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

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

No annotations are provided, so the description carries the full burden. It does disclose a meaningful constraint on the output (privacy-conscious, no invented facts, commitments, or relationship history), which is real behavioral context, but it never states that the tool is read-only/stateless or what the guidance actually looks like.

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?

A single front-loaded sentence with no filler; the integrity constraint is attached directly to the purpose rather than buried in a second paragraph.

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 guidance tool with no annotations and no output schema, the description is adequate on purpose but omits two things an agent would want: what the returned guidance looks like and what the tone parameter controls. Minimum viable rather than complete.

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 0% and the description never mentions the sole parameter, "tone". The enum values (simple, warm, gentle) are largely self-explanatory, so the description's total silence is survivable, but it fails to compensate for the coverage gap.

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 ("Get guidance") and resource ("writing a caring message") with an added qualifier about the content's integrity constraints. It is clear on its own, but it never distinguishes itself from the sibling find_writing_help, which sounds like it could cover the same need.

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?

Usage is only implied by the phrase "writing a caring message" — there is no explicit when-to-use statement, no prerequisites, and no naming of find_writing_help as an alternative or complement. An agent can infer the context but gets no routing guidance.

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