springboot_verify_mappings

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

Beyond the readOnly/idempotent/non-destructive annotations, the description adds two pieces of real behavioral context: it does not send requests to the application's business URLs, and a registration match does not imply the request will succeed. That second caveat is important for interpreting results and is not derivable from 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?

It is a single compact sentence-pair with the purpose front-loaded and no filler. The two negative caveats are slightly compressed into the same clause chain, but nothing is wasted.

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?

An output schema exists, so return-value explanation is rightly omitted, and the annotations cover the safety profile. However, with 7 parameters, a required-anyOf constraint, and pagination via cursor/maxResults, the description leaves an agent without guidance on required inputs or result-size limits, so it is only adequate rather than complete.

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 only 29%, with 7 parameters, and the description explains none of them: cursor, maxResults, targetId, and contextId are entirely unaddressed, and the anyOf requirement (at least one of pathPattern/httpMethod/controllerClassPattern) is not mentioned. Even the two glob patterns that carry schema descriptions get no added meaning. The description does not compensate for the coverage gap.

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 opens with a specific verb and resource set: it returns unified MVC/WebFlux routes, handlers, and method descriptors. An agent can tell this is a route-registration inspection tool rather than a bean/config/drift inspector. It stops short of naming a sibling such as springboot_search_openapi, which also deals with request mappings, so differentiation is only partial.

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?

It states a concrete trigger — call it when troubleshooting a path, HTTP method, or Controller that is not registered — which is a clear positive condition for use. It gives no explicit exclusion or named alternative for when to prefer springboot_search_openapi, so the guidance is clear but not complete.

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