numerai_status

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds important behavioral context: 'no API calls made' (ensuring low cost), 'env vars as booleans (never key values)' (clarifying output format), and 'NUMERAI_SECRET_KEY never appears' (addressing security). This goes beyond what annotations provide.

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 two sentences succinctly covering purpose, output specifics, and safety. No redundant words. It is front-loaded with the core purpose.

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 no parameters, no output schema, and comprehensive annotations, the description provides sufficient context for an agent. It lists key output categories and emphasizes safety. It could be slightly more explicit about all returned fields, but it is adequate for a status check 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?

There are no parameters (0 params, 100% schema coverage), so the baseline is 4. The description does not need to add parameter information, and it doesn't. This is appropriate.

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 it returns Numerai tournament configuration status, listing specific items like env vars as booleans, dataset version, round cadence, and proxy_mmc labeling notes. This distinguishes it from the many sibling tools, all of which have different specific purposes.

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 explicitly states 'Safe to call anytime — no API calls made,' which guides the agent on when it is appropriate to use. It does not explicitly mention when not to use it or provide alternatives, but the context is sufficiently clear for this simple read-only tool.

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