get_bridges_v1_graph_bridges_get

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

With no annotations, the description must disclose behavioral traits. It only states it's a public GET request. It fails to explain what 'bridges' or 'betweenness centrality' entail, whether results are ordered, or if the limit parameter implies pagination. The description is insufficient for an agent to understand side effects or data retrieval behavior.

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 extremely concise (one line) and front-loads the HTTP method and visibility. However, the brevity sacrifices informative content. It earns a high score for conciseness but not for completeness.

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 tool's single parameter and lack of annotations or output schema, the description should explain core concepts like 'bridges' and 'centrality' and clarify that this is a list endpoint. Without these, an agent cannot confidently decide to use this tool over others.

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%, so the description must add meaning beyond the schema. However, it does not mention the 'limit' parameter at all, leaving the agent to infer its purpose solely from the schema's type and constraints (integer, 1-100). This is insufficient.

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 action ('Get'), the resource ('top bridge datasets'), and the specific metric ('by betweenness centrality'). It uniquely distinguishes this tool from sibling tools like 'get_communities' or 'get_neighbors' by specifying a graph centrality measure.

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 explicit guidance on when to use this tool versus alternatives. The 'public' label hints at accessibility, but there is no mention of prerequisites, limitations, or scenarios where this tool is preferred over similar graph-analytics endpoints.

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