save_to_daily_note

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

With no annotations provided, the description must fully disclose behavioral traits. It only states the basic action and does not explain whether content is appended or overwritten, what permissions are required, or any side effects. This is a significant gap for a mutation tool.

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 description is a single concise sentence with no filler, which is structurally efficient. However, it is under-specified, missing essential details about parameters and behavior, so the brevity is not a virtue in this context.

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 the tool's moderate complexity (nested requestBody, no output schema, no annotations), the description is far from complete. It does not mention that spaceId and mdText are required, nor describe what the tool returns, making it inadequate for safe invocation.

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 has one nested requestBody with fields like spaceId and mdText, but the description does not explain any of them. With 0% schema description coverage, the description completely fails to compensate, leaving parameter meanings ambiguous.

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 'Save text to today's daily note' clearly identifies the action (save text) and the resource (today's daily note), which distinguishes it from sibling tools like save_weblink (saving URLs) and search_content. However, it lacks elaboration on what 'text' means or the note's context, but the core purpose is unambiguous.

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 provides no guidance on when to use this tool versus alternatives such as save_weblink or search_content. There is no mention of prerequisites, preferred use cases, or exclusions, leaving the agent without direction on selection.

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