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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds one thing beyond them: that the return is a text format accompanied by a complete worked example, which is meaningful given there is no output schema. It says nothing about the size of that example or whether the format is stable across calls, which is the remaining useful detail.

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?

Two short sentences, zero waste, with the primary action and return content front-loaded before the usage qualifier. Every clause carries information an agent would act on.

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, non-destructive reference tool with no output schema, the description covers what it returns and when to call it, which is essentially everything an agent needs. The only omission is an indication of how large the returned example is, which could matter for context budgeting.

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 and the schema is empty with additionalProperties=false, so there is nothing for the description to disambiguate. A baseline 3 applies; no parameter meaning is added or needed.

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?

States a specific verb and resource ('Returns the Notematics text format') plus the shape of the payload ('with a complete example'), so the agent knows this is a format-spec lookup, not board content. It is clearly distinct from read_board and add_to_board, though it never names a sibling explicitly.

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?

'Read it before writing a board' gives an explicit trigger, and 'unless you already have it' gives an explicit exclusion, which is unusually good routing guidance for a reference tool. It stops short of naming add_to_board as the operation this is a prerequisite for, so the linkage is implied rather than stated.

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