swpc_solar_wind

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

With readOnlyHint=true annotation, the description adds value by disclosing the specific data components (density, speed, temperature, Bz, Bt) and explaining the scientific significance of southward Bz. This goes beyond the annotation without contradicting it.

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 concise at three sentences, front-loaded with the main action, and every sentence adds value: purpose, data fields, and domain context. No fluff or redundancy.

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?

Although there is no output schema, the description adequately explains the data content and time range (7-day) for a simple read-only tool with one optional parameter. It does not describe response format or units, but that is not critical for this simple retrieval.

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 the parameter semantics are fully documented in the schema. The description repeats the same field breakdown (plasma vs mag) and provides no additional parameter-specific details beyond the schema.

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 'Get 7-day solar wind data' with a specific verb and resource. It distinguishes from sibling SWPC tools by focusing on solar wind plasma and magnetic field data, not alerts or indices.

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 implies usage: if you need solar wind plasma/magnetic field data, use this tool. It provides context (7-day, types of data) but does not explicitly name alternatives or exclusions, relying on sibling tool names for differentiation.

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