sdss_query

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

No annotations are provided, so the description carries the full burden. It does not mention that queries are read-only, what authentication or network access is needed, rate limits, or that results may be truncated by max_results. It reveals only the supported lookup modes.

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?

A single tight sentence front-loads the resource and enumerates the three modes with no filler. Every clause earns its place.

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?

The description names the query modes, which is the minimum needed to select a query_type, but with 11 parameters, no annotations, and no output schema, it leaves out return format, result limits, and safety profile. Adequate but with clear gaps for a tool of this complexity.

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 schema already documents every parameter, including which apply to which query type. The description adds no parameter semantics beyond naming the three query types, which the schema already encodes as an enum. Baseline 3 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?

States a specific verb (Query) and resource (SDSS DR18) and enumerates three supported query modes, making the tool's scope clear. It does not, however, distinguish itself from siblings like simbad_query or ned_query that also do astronomical lookups.

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 lists query modes but gives no guidance on when to use this tool versus the many sibling astronomy query tools, nor any prerequisites or exclusions. An agent cannot tell from the text when SDSS is the right choice.

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