get_note_instructions

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

With no annotations provided, the description carries the full burden and does well: it discloses that the tool is read-only, takes no arguments, makes no network calls, and that the returned rules are static. This exceeds a minimal viable description, though it could add more detail about the exact structure of the returned instructions.

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 information-dense but every sentence earns its place: first sentence defines the core purpose and output, second states key behavioral constraints, third gives direct usage guidance. It is front-loaded with the most important information and has no filler or redundant repetition.

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 tool with no parameters, no output schema, and simple read-only behavior, the description fully covers what an agent needs to invoke it correctly: what it returns (rules for writing standup notes), behavior (read-only, no network), and when to call it (once before first note). Nothing essential is missing.

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 has zero parameters, so the schema provides no semantic information. The description explicitly states 'no arguments', which confirms the interface. Baseline for zero parameters is 4, and the description's explicit mention adds no extra parameter semantics beyond stating there are none.

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 the tool returns note-writing rules and explicitly ties them to transforming get_standup_data output into a speakable standup note. It distinguishes itself from sibling tools by describing its role in the pipeline (before writing the note), making its purpose unambiguous.

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 provides clear usage context: call it once before writing the first note, and notes the rules do not change between calls. It does not explicitly mention when not to use it or alternative tools, but for a zero-argument read-only tool with no siblings that overlap, this is sufficient and not misleading.

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