Story

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

No annotations are present, so the description carries the full burden of disclosing side effects. It names the operations but does not explain what update/remove permanently change, what 'promote' does to an entry, or whether operations are reversible. 'Manage' only implies mutation rather than describing consequences.

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 purposeful sentences: the first defines the resource and content types, the second gives explicit use and non-use guidance. No filler and no repetition of schema details.

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 multi-action CRUD tool with no annotations or output schema, the description plus the fully documented schema covers selection and basic invocation well. The only real gap is operational semantics of promote/remove, which the description leaves to inference, so it is not a perfect 5.

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 coverage is 100% and each parameter already has a description noting the action it applies to (e.g., 'Story entry text (record/update)', 'Optional page size (list)'). The description adds domain framing but no parameter-level detail beyond the schema, so baseline 3 is appropriate.

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 opens with a specific verb-resource pair ('Manage the story journal'), enumerates the allowed entry types, and lists the five operations. It also differentiates itself from the lore tool by stating the domain boundary, so an agent can distinguish story from siblings like lore and note.

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?

Explicit 'Use when' conditions cover all five supported actions, and the 'Do NOT use when' clause names the exact alternative (lore, action: set) for durable world facts. This is textbook when-to-use routing.

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