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

Annotations already declare readOnly, idempotent, non-destructive and closed-world. The description adds real behavioral context beyond them: it enumerates included fields (sensors, entrant, SHA-256 provenance) and disclaims side effects ('No database access, simulation launch, external network or LLM call').

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?

Core purpose and the parameter note are front-loaded, and each sentence is short. A few trailing negations ('Koi are decorative and unranked') feel defensive but are arguably needed to set expectations for a synthetic exhibition feed.

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?

An output schema exists, so return values need not be explained, and the annotations cover the safety profile. Between the description's payload summary and exclusions, an agent has enough to invoke it correctly, though the relationship to sibling bamboo tools remains unstated.

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?

With 0% schema description coverage, the description carries the burden and does add meaning: 'day' is interpreted as day-of-year in the 1-365 range, with the default resolving to the current UTC day of year. The range itself duplicates the schema, but the semantic interpretation of the parameter is genuinely added.

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 ('Read one day ... of the published Rust bamboo replay used by the 3D scene') and clarifies the payload includes sensors, entrant and SHA-256 provenance. It is clear what the tool does, though it does not explicitly name which sibling (e.g. bamboo_training_artifact or bamboo_challenge_get) it is distinct from.

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?

Provides scope exclusions ('not an observation, strategy evaluation or hydraulic forecast' and 'Synthetic exhibition only'), which narrows when it applies. However, it never names an alternative sibling or states the condition that would route an agent to a different bamboo/farm tool, leaving usage largely implied.

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