get_endstops

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds a genuinely useful behavioral fact beyond that: the call does not move any axis, so endstops can be safely triggered by hand during the read. It does not describe the response payload, but with a safety profile already provided by annotations this is minor.

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 tight sentences, zero filler. The core behavior is front-loaded and the usage note follows immediately after.

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 sensor read with no output schema, the description covers what is returned (triggered-or-not per axis), what does not happen (no motion), and the intended diagnostic workflow. Nothing material is missing.

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 zero parameters, so there is nothing to disambiguate; the baseline for a parameterless tool is 4. The description correctly implies no arguments are needed ('per axis' results come back generically).

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 and resource ('get_endstops' → current endstop states per axis) and immediately scopes it with the qualifier 'without moving anything'. An agent can distinguish this from get_sensors/get_status because it is explicitly about endstop trigger states, not general sensor readings.

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?

Gives concrete usage context: check wiring by pressing each endstop by hand before homing. This tells the agent exactly when the tool is useful, though it names no alternative tools and states no explicit when-not-to-use condition.

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