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

Annotations already establish that this is a safe read (readOnlyHint=true) against a closed dataset (openWorldHint=false), so the safety burden is lifted. The description adds genuinely useful behavioral context beyond that: a personal Storskarvia API key must be supplied as a Bearer token, which tells the agent something about auth failure modes.

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 resource definition is front-loaded ahead of the auth prerequisite. It is a noun phrase rather than a verb-led statement, which slightly weakens the opening, but nothing is wasted.

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?

An output schema exists, so return values need not be described, and with zero parameters the call surface is fully covered by the schema. The remaining gap is contextual routing: nothing tells the agent how this relates to the other nine Storskarvia tools.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The absence of filters is consistent with the schema and with the 'my projects' scoping in the name.

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 names the resource precisely (the authenticated user's Storskarvia projects) and disambiguates what a 'project' is with concrete examples (novels, screenplays, video scripts). It lacks an explicit verb like 'list', so the retrieval action is inferred from the name rather than stated, and it does not contrast itself against the sibling tools.

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?

There is no statement of when to call this versus alternatives such as get_skarvia_info or list_guides, no prerequisite guidance beyond the auth note, and no exclusion conditions. The agent must infer that this is the entry point for enumerating the user's own content.

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