postit.create

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without mentioning side effects, return values, permissions, or error conditions. For a create operation, important behavioral details are absent.

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 succinct sentence with no redundant words. It is effectively concise, though it lacks structural detail. The brevity is acceptable but does not provide added value beyond a minimal statement.

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?

The tool has multiple parameters and an output schema, yet the description provides no context about parameter semantics, usage scenarios, or expected behavior. The presence of an output schema mitigates the need to explain return values, but the description remains insufficiently complete for an agent to invoke it correctly without additional guessing.

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 input schema has three properties (name, body, dir) but the description provides zero parameter information. With schema description coverage at 0%, the description was expected to compensate, but it mentions none of the parameters or their meanings.

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 'Create a new postit note' uses a specific verb ('Create') and a clear resource ('postit note'), distinguishing it from sibling tools like postit.rename or postit.delete. It is direct and unambiguous, fulfilling the purpose clarity criterion.

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 topic.create or other postit operations. It lacks context about prerequisites, exclusions, or scenarios where a different tool would be more appropriate.

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