apex_add_breadcrumb

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

Annotations are all false, so the description carries the burden of behavioral disclosure. It only says 'Add' without mentioning side effects like creating/updating a region, whether existing breadcrumbs are replaced, or if any page prerequisites exist. This is a significant gap for a mutation tool.

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 a single, front-loaded sentence that immediately conveys the core purpose. It contains zero unnecessary words and is easy to parse.

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?

While the schema is thorough and an output schema exists, the description lacks essential behavioral context for a write operation, such as what side effects occur or whether it requires an existing page. It is adequate for a simple tool but does not fully compensate for the annotation gaps.

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 input schema has 100% parameter coverage, providing detailed descriptions for entries, page_id, sequence, and region_name. The description's mention of the entry format is redundant with the schema and adds no extra semantic value, so the 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?

The description clearly states the tool's action ('Add') and resource ('breadcrumb navigation') and even specifies the entry format. It distinguishes from siblings like apex_add_nav_item by explicitly targeting breadcrumbs, and no other sibling handles this exact resource.

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 implies when to use the tool (when you want to add breadcrumb navigation) but provides no explicit guidance on when not to use it or what alternatives exist. There are no sibling tools specifically for breadcrumbs, so the usage context is inferred from the purpose.

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