Trace a Colour Through History

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

Annotations already declare readOnlyHint=true, and description confirms a read operation by describing historical tracing. Adds context about chronological order and example but does not disclose any additional behavioral traits (e.g., data sources, limits).

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?

Four sentences, each adding value: core action, elaboration, importance statement, and illustrative example. Front-loaded with key task, no filler. Within typical length guidelines.

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?

Given low parameter count, presence of annotations, and existence of output schema, the description covers purpose, value, and an example. Slight gap: no mention of the scope of historical data (timeline length, cultures covered), but overall adequate for a straightforward lookup 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?

Schema description coverage is 100%, so baseline is 3. Description adds an example of usage but does not significantly enhance parameter meaning beyond what the schema already provides (hex field description, tolerance default).

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?

Description uses specific verb 'traces' and resource 'colour's appearances across cultures and centuries in chronological order', clearly distinguishing from siblings like colour_story by emphasizing chronological order and historical depth. Includes a concrete example (deep blue) that reinforces the purpose.

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?

Description says 'Essential for understanding why a colour carries the weight it does', implying usage context but does not explicitly state when to use this versus alternatives like colour_story or colour_forensics. No when-not-to-use or exclusion criteria provided.

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