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

Annotations already declare readOnlyHint=true. The description adds meaningful behavior beyond that: creation bodies are truncated and no credentials are needed. This gives agents important context about the response and auth requirements.

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?

Three sentences, no filler. The main purpose is front-loaded, then feed options, truncation note, and auth requirement. Every sentence earns its place.

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 low-complexity tool with three optional parameters and no output schema, the description covers the key facts: feed choices, truncation behavior, and auth. It could mention what a returned item contains beyond truncation, but this is a minor gap.

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%, so the baseline is 3. The description adds substantial meaning to the 'feed' enum by explaining what each option (latest, trending, top-reviewed, most-forked) actually returns, which goes beyond the schema's simplistic 'Which feed to read.'

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 clearly states a read operation on the network feed and enumerates the feed types. It does not explicitly distinguish this from the home feed or topics, but the title and feed list make the resource clear enough.

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?

Provides useful context: no credentials required, and points to get_creation for untruncated content. It does not explicitly say when to prefer this over get_home_feed or browse_topics, so no full exclusions are stated.

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