Read home feed

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

The annotation readOnlyHint=true already signals a safe read, and the description adds valuable behavioral context: 'light snapshot' indicates possibly incomplete data, and 'best-effort' plus 'layout changes often' warn of variability. This goes beyond the annotation and helps calibrate expectations.

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, front-loaded sentence that conveys purpose and key caveats without filler. Every word earns its place, making it highly concise and clear.

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 is simple with one optional parameter and a read-only annotation, but there is no output schema. The description tells what the tool does and warns about its limitations, yet it doesn't describe the return format or contents, leaving a minor gap for a 'snapshot' tool.

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 description does not mention the 'limit' parameter at all, and schema description coverage is 0%. The parameter exists in the schema with min/max constraints, but the description offers no guidance on how to choose the limit, leaving the agent without added meaning.

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 uses the specific verb 'Read' and clearly identifies the resource as the 'home feed', which distinguishes it from siblings like create_post and list_my_posts. The phrase 'light snapshot' adds useful nuance, though it doesn't explicitly contrast with similar read 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?

The description implies usage for lightweight, best-effort reads but does not explicitly state when to use this tool versus alternatives like list_my_posts. The caveat about layout changes hints at suitability but no exclusions or sibling comparisons are provided.

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