get_data_schema

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

With no annotations, the description fully carries the burden. It discloses that the tool returns a JSON Schema specification and enumerates the major contents (required columns, naming conventions, constraints, date formats). It also implies a read-only, side-effect-free 'get' operation, though it doesn't explicitly say so.

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 concise sentences: the first states the tool's purpose, the second lists exactly what the returned schema covers. Every sentence earns its place with no filler or 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 parameterless getter, the description is complete: it names the resource, the return type, and the categories of information inside the returned schema. No additional detail about parameters or side effects is needed, and there is no output schema requiring separate explanation.

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 there are no parameter semantics to explain. The baseline for a no-parameter tool is 4, and the description adds meaningful context about what the returned schema contains without needing to document inputs.

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 ('Get') and a specific resource ('canonical CSV data schema for Simba MMM input files'), and clarifies that it returns a JSON Schema specification. The scope is unambiguous and clearly distinct from sibling tools that handle runs, models, or uploads.

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 makes clear this is the tool to use when you need the schema for Simba MMM input files, which is useful context before uploading or validating data. It doesn't mention explicit exclusions, but no close alternative exists among the siblings, so no when-not guidance is necessary.

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