get_settings

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a pure read via 'Get' and discloses the categories of data surfaced, but says nothing about permissions, whether values are global versus scoped, or how results are shaped. It does not contradict anything, but for a tool with zero annotation coverage it leaves real behavioral questions open.

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 front-loaded sentence with a clean three-item enumeration and no filler. It is appropriately sized for a zero-parameter read tool, with only minor ambiguity in how the three content groups relate to one another.

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?

With no parameters and no output schema, the description is the only source of return-value information, and it only sketches three content categories. It does not indicate whether the response is a single flat object or grouped sections, nor what the metrics mean. Adequate to select the tool, thin for interpreting its output.

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 takes no parameters, so there is no parameter semantics to add and the baseline of 4 applies. The description correctly does not invent inputs or imply optional filters that the empty schema would not support.

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 names a specific verb ('Get') and enumerates the concrete resources returned: embedding completion metrics for StarSystems and CelestialBodies, active embedding/LLM parameters, and context window presets. That content profile is distinctive enough to separate it from entity getters like get_celestial_body or get_star_system, though it never explicitly contrasts itself with a sibling. The mild tension between the name 'get_settings' and the metrics-oriented content is resolved by the enumeration itself.

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?

There is no statement of when to call this versus alternatives, no prerequisites, and no exclusions. The agent must infer from the content list that this is a configuration/status inspection tool rather than an entity fetch. No routing guidance is offered at all.

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