find_bored_bosses

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

Annotations already declare readOnlyHint=true. The description adds that it is diagnostic and lists the specific details reported. No contradictions and provides useful behavioral context beyond annotations.

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 to three sentences, front-loaded with the main action and details. Every sentence provides essential information without redundancy. Highly concise.

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?

Tool has a single optional parameter and an output schema. The description lists reported items but does not explain the input parameter. Given the low complexity, the gap in parameter guidance makes it incomplete.

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?

Only one optional parameter 'object_name' with default empty string. Schema coverage is 0%, but description does not explain what the parameter represents or how to use it. The description mentions 'extending a boss' but does not connect to the parameter, leaving ambiguity.

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 tool finds candidate bored bosses and reports specific evidence (bore opening location, axis, diameter/depth, cap faces, etc.), distinguishing it from sibling tools like 'find_bosses' which likely find generic bosses.

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?

Explicitly states when to use: 'before extending a square/rounded-square boss with a central bore.' Also clarifies it is 'read-only and diagnostic, not proof.' No explicit alternatives mentioned, but the context is clear.

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