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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful context beyond that: the provenance tagging scheme ('by founder' vs 'by shipfound') and the conditional nature of the open question ('if there is one'), plus 'Free' implying no cost. It stops short of describing the return shape or ordering.

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?

It is a single compact sentence plus a 'Free.' fragment, so length is fine. However, the opening clause 'The notes grow's judge reads every day' is convoluted and buries the actual action, and the trailing 'Free.' is a dangling sentence fragment rather than integrated information.

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 zero-parameter read tool with annotations covering safety and no output schema, the description does the necessary work of telling the agent what content will come back (rules/facts, learned observations, open question). Only minor gaps remain, such as not confirming the notes are returned as a list or how empty states are represented.

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 the baseline is 4. The description correctly implies no inputs are needed and frames the call as a simple fetch of existing notes.

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 (the notes grow's judge reads) and enumerates its contents — founder rules/facts, Shipfound's learned observations, today's open question — but never states a verb like 'returns' or 'lists', so the agent must infer retrieval from context. Titles such as 'What Shipfound knows about this founder' restate the resource rather than differentiate it from siblings like notes_context or grow_notes_save.

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 explicit statement of when to call this versus notes_context, notes_save, or grow_notes_save. The only routing signal is indirect: 'The founder edits them in the results app' implies this tool is for reading and editing happens elsewhere, which an agent must infer.

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