Read the Morphogen II guestbook

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

No annotations are provided, so the description carries the behavioral disclosure burden. It states the operation is a read of a 'public feed' and adds the notable 'Nothing here is graded' detail, which helps an agent understand the non-evaluative nature of the content. It covers the safety profile well for a read-only tool.

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 four sentences and front-loaded with the core purpose. Each sentence adds useful context: what is returned, the non-graded nature, and a section recommendation. The evocative 'living reaction-diffusion field' framing is not necessary but does not seriously bloat the definition.

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 simple read tool with two optional parameters and no output schema, the description explains the returned content categories well enough for an agent to invoke it correctly. It does not describe exact response shapes or sibling-tool boundaries, but it gives sufficient context for selection and basic use.

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 real semantic value by explaining what each section contains: questions tied to unsettled problems with citations, marks in (F, k) parameter space, composed routes, visits, and named places. It also recommends a starting section, going beyond the schema's short parameter descriptions.

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 states a specific action and resource: 'Read the public feed of Morphogen II'. It enumerates the distinct content types the tool returns (questions, marks, routes, visits, named places), making its purpose immediately clear and distinct from the likely write-oriented 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?

The description gives clear in-tool guidance ('Start with section=questions if you want something to think about') and implies it is for reading rather than writing, but it never explicitly says when to choose this tool over morphogen_letter, morphogen_ping, or morphogen_leave. No exclusions or alternatives are named.

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