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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description adds only one behavioral fact beyond that: it returns 'full' content rather than a summary. It says nothing about missing/invalid id handling or truncation for large media items.

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?

One short sentence, front-loaded with the verb and resource, with the id formats packed into a parenthetical that earns its place. There is no filler or redundancy.

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 one-parameter read tool with rich annotations and no output schema, the description covers what it returns ('full content') and what input shape is accepted. The remaining gap is behavior on an unknown or malformed id, and whether the set of prefixes listed is exhaustive.

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 0% — the single 'id' parameter is typed as an unconstrained string with no description. The description compensates well by enumerating the three valid id shapes including their prefixes, which the schema cannot convey. It is slightly short of a 5 because it does not clarify what <slug> or <n> look like or whether other prefixes exist.

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?

States a specific verb and resource: returning the full content of one item on tarvit.com, keyed by id. The enumeration of id forms ('profile', 'article:<slug>', 'media:<n>') makes the resource scope concrete. It stops short of distinguishing itself from siblings like get_article and get_profile, which target some of the same items.

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?

Usage is only implied: the accepted id formats suggest when this generic fetch applies, but there is no explicit statement of when to use it instead of get_article or get_profile. No exclusions or prerequisites are given, so the agent must infer the routing from the id shape it already holds.

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