Bear Notes Capabilities

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

Annotations indicate readOnlyHint=true and idempotentHint=true. Description adds context that the tool reports current mode and unlock instructions, which goes beyond annotations. It does not contradict annotations and clarifies the tool is informational.

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?

Description is two sentences with no filler. It is front-loaded with the core action and then adds usage guidance. Every sentence earns its place.

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 no parameters, no output schema, and a simple task, the description is sufficient. It explains the tool's purpose and when to use it. Could mention what specifically 'reporting mode' outputs, but it is adequate.

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?

Tool has no parameters, so the schema coverage is effectively 100%. Description adds no parameter info, but with zero parameters this is not needed. The baseline for 0 parameters is 4, and the description meets it.

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?

Description explicitly states the tool reports the current mood and how to unlock additional capabilities. Verb 'Report' and resource 'Bear Notes MCP server mode' are specific and distinct from sibling tools like bear-search-notes or bear-list-tags.

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?

Description provides explicit scenarios for when to call: when user asks what can be done with Bear notes, when write operations seem unavailable, or when user wants to enable note creation/editing/tag management. This clarity helps the agent choose this tool over alternatives.

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