beacon_info

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

No annotations provided, so the description must reveal behavioral traits. It only says 'get details' without specifying what details are returned, whether the operation is safe, or any side effects. Lacks disclosure of permissions or rate limits.

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 very concise (5 words), but at the expense of necessary detail. It loses points for under-specification rather than brevity.

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?

Given the absence of output schema and annotations, the description should explain what 'details' are returned. It is incomplete for an information retrieval tool with one parameter.

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 0%, yet the description adds no meaning beyond 'by id'. It does not specify the format or source of 'beacon_id', nor does it explain what constitutes a valid identifier.

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 the verb 'get' and resource 'details for one beacon' with the identifier 'by id'. It is specific but does not distinguish from sibling tools like 'list_beacons' or 'session_info'.

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?

No guidance on when to use this tool versus alternatives such as 'list_beacons' for multiple beacons or 'session_info' for sessions. No context on prerequisites or limitations.

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